butt_mountain_69420

I've just about got this Docker thing licked. After hundreds of hours, I finally get it, and my dusty millenial ass has joined the 21st century.

-but we have issues

==============================xxxx==============================

The environment:

I have multiple containers running on my local network, including photoprism, Kavita, and Filebrowser. I also installed Heimdall as a startpage. On the local network everything works great.

The entire goal of this project is to have these services accessible from outside the house, from my mobile devices but also with the ability to share links and files with friends.

==============================xxxx==============================

The problem:

Enter Tailscale. I tried port forwarding, having a domain, all that jazz, but it ended up being way too complicated. I don't want just anyone to access my shit, I only want a handful to be able to use services of my choosing in accordance with the user permissions I set up for them. Tailscale was the first thing I tried that worked.

I added my docker instance to tailscale, and when you access the machine, you are correctly taken to my Heimdal start page. Unfortunately, when you click on the icons for my docker services, the browser gives you an "unable to connect" error.

Under my Tailscale admin panel, the services are listed along with their port and IP information. Heimdall (443) and Portainer(8000) are listed as https and http under "type", as expected. The remaining services are listed as "other." (the portainer link doesn't work either)

• Has anyone else dealt with this?

• If this has to do with ports, is there an easy way to configure ports without having to re-run the images and make new containers?

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.