FileBrowser running at 7777:80 in Docker Desktop
(7777 was chosen by me to preemptively avoid conflicts)
ATT Router with custom service “Filebrowser” global range 443, TCP, Host Port 443
(443 was chosen by me because I want the site to only be accessible if secure)
Custom firewall exception, tcp, local 7777, Host 443
Filebrowser login page accessible from localhost:7777
Filebrowser login page accessible from http://my_custom_duckdns_domain:7777
Not accessible from https:
Not accessible from external device.
Tried to run Win-Acme, failed.
Tried to run Caddy:
"Error: loading initial config: loading new config: http app module: start: listening on :80: listen tcp :80: bind: An attempt was made to access a socket in a way forbidden by its access permissions."
caddy is not a docker image
I’ve been using ChatGPT to help me configure this stuff, it has not been going well. The AI can’t remember what it tells me from one question to the next, so you end up in loop after loop of errors.
I ended up deleting the caddyfile because no configuration supplied by ChatGPT worked.
Can anyone help me get this going?
I’d really like to understand how to safely expose the fileserver, but nothing is working.
I already tried nextcloud, and though it looks pretty, the on-board office suite, which I want so you don’t have to download a file to view it, will not function because Collabora won’t download.
When you tried caddy and received an error, that looks like you are getting the wrong image name.
Then you mentioned deleting caddyfile as the configuration didn’t work. But, if I am following correctly the caddyfile wouldn’t yet be relevant if the caddy container hadn’t actually ran.
Pulling from Caddys docs, you should just need to run
I have not tried caddy through docker yet, just running it through a windows command line with admin priv. I’m looking into doing it with Docker, just haven’t started yet.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
When you tried caddy and received an error, that looks like you are getting the wrong image name.
Then you mentioned deleting caddyfile as the configuration didn’t work. But, if I am following correctly the caddyfile wouldn’t yet be relevant if the caddy container hadn’t actually ran.
Pulling from Caddys docs, you should just need to run
Where $PWD is the current directory the terminal is currently in.
Further docs for then configuring for HTTPs you can find here under
https://hub.docker.com/_/caddy
I have not tried caddy through docker yet, just running it through a windows command line with admin priv. I’m looking into doing it with Docker, just haven’t started yet.
I will remember how familiar you are with docker!