0
Exposing Myself (with Filebrowser) (lemmy.world)
submitted 10 months ago* (last edited 10 months ago) by butt_mountain_69420@lemmy.world to c/selfhosted@lemmy.world
9 comments fedilink hide all child comments

Win11 Pro on used lenovo thinkcentre

Docker Desktop

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.

I do not claim to know what I am doing.

I dislike CLI, and Linux frustrates me to no end.

I'm open to any suggestions you all have.

you are viewing a single comment's thread
view the rest of the comments
[-] breadsmasher@lemmy.world 1 points 10 months ago

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

$ docker run -d -p 80:80 \
    -v $PWD/Caddyfile:/etc/caddy/Caddyfile \
    -v caddy_data:/data \
    caddy

Where $PWD is the current directory the terminal is currently in.

Further docs for then configuring for HTTPs you can find here under

Automatic TLS with the Caddy image

https://hub.docker.com/_/caddy

[-] butt_mountain_69420@lemmy.world 1 points 10 months ago

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!

this post was submitted on 04 Jan 2024
0 points (50.0% liked)

Selfhosted

39700 readers
676 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 1 year ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz