Replies: 1 comment
-
The compose seems overly complex. I'm running NPM as a separate Docker container. Deployed FB with this; services: Then just added a proxy host with a wildcard cert from LetsEncrypt in NPM. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
nginx proxy file nginx/proxy_host/9.conf
filebrowser config filebrowser/settings.json
If I have location /filebrowser {
and "baseURL": "/filebrowser",
I can get:
https://filebrowser.MYDOMAIN/ gives an OpenResty page
https://filebrowser.MYDOMAIN/login gives a 404
http://127.0.0.1:82/login loads the login page
http://127.0.0.1:82/test redirects to the login page
So I feel like that is very close to working.
Putting an ending / on the end of baseURL doesn't change anything.
So I though maybe the filebrowser web page is trying to redirect me, so maybe it needs the full URL...
If I have location /filebrowser {
and "baseURL": "https://filebrowser.MYDOMAIN/filebrowser",
I can get:
https://filebrowser.MYDOMAIN/ gives an OpenResty page
https://filebrowser.MYDOMAIN/login gives a 404
http://127.0.0.1:82/login gives the 3 dots "stuck" page
So that's clearly not right since I can't get in at all.
Just showing what I had originally using the defaults...
If I have location / {
and "baseURL": "",
I can get:
https://filebrowser.MYDOMAIN/ gives a 502 bad gateway
https://filebrowser.MYDOMAIN/login gives a 502 bad gateway
http://127.0.0.1:82/login loads the login page
http://127.0.0.1:82/test redirects to the login page
This is where I was stuck for a long time, but eventually found that entering a custom baseURL gets me close.
BTW: Entering just "/" for baseURL doesn't change anything, you need a name, and sync that with the npm config.
NPM has a LetsEncrypt certificate, and trying http from outside will pisss off cloudflare with a "bad cert" message.
I also want everything coming through https. But can anyone get me past that last little step to get the loading page.
My docker-compose.yml just in case it's significant:
I didn't have the VIRTUAL_HOST and PROTO orignally, that was something I found along the way.
I can include other bits if necessary.
Nothing is showing up in either docker log to indicate why I can't reach the login page.
The most helpful link I found is #400 which is what got me close.
Beta Was this translation helpful? Give feedback.
All reactions