this post was submitted on 02 Jul 2023
16 points (86.4% liked)

Selfhosted

40763 readers
968 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I was trying to setup filebrowser behind swag with docker in the same docker network but for some reason it just doesn't wanna work.

I even added the FB_BASEURL=/filebrowser env variable after reading the github issues but still no luck.

I'm getting 502 bad gateway with swag.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (1 children)

Uhh apparently posted on ur other thread https://ymmel.nl/comment/128500

Can you reach file browser regularly? Attach it to a bridge network and expose the correct port to see if the container is running properly. Or check the docker logs for it. Could be that the reverse proxying isn’t working but I’d check the actual container first and go from there.

[–] screx 1 points 2 years ago

Yeah, I figured it out... the container was named "filebroswer" instead of "filebrowser"