I
Immich6d ago
Schoof

Setting up Immich on home NAS (UGREEN). But failing to make it https publicly available

Hello I've managed to set up Immich on my NAS using portainer. I used the following setup: https://docs.immich.app/install/portainer This was very quick and easy, is this still the correct way to set up Immich? Now I want to make Immich publicly available (for my family). I have a domain that is setup with DYNDNS to my home IP. I have tried the following: - Install NgInx Proxy Manager with the following docker compose:
services:
nginx-proxy-manager:
image: nginxproxymanager/nginx-proxy-manager-dev:pr-4836
container_name: Nginx-Proxy-Manager
healthcheck:
test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/81' || exit 1
interval: 10s
timeout: 5s
retries: 3
start_period: 90s
volumes:
- /volume1/docker/npm/letsencrypt:/etc/letsencrypt:rw
- /volume1/docker/npm/data:/data:rw
- /volume1/docker/npm/tmp/le_logs:/tmp/letsencrypt-log
environment:
TZ: Europe/Brussels
ports:
- 443:443
- 81:81
- 80:80
restart: on-failure:5
services:
nginx-proxy-manager:
image: nginxproxymanager/nginx-proxy-manager-dev:pr-4836
container_name: Nginx-Proxy-Manager
healthcheck:
test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/81' || exit 1
interval: 10s
timeout: 5s
retries: 3
start_period: 90s
volumes:
- /volume1/docker/npm/letsencrypt:/etc/letsencrypt:rw
- /volume1/docker/npm/data:/data:rw
- /volume1/docker/npm/tmp/le_logs:/tmp/letsencrypt-log
environment:
TZ: Europe/Brussels
ports:
- 443:443
- 81:81
- 80:80
restart: on-failure:5
- Set it up as follows (see attachment 1) - Port forward in my router as follows (see attachment 2) Now when I visit the https:// of my domain (with the port added) I get the error:
An error occurred during a connection to ... SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
An error occurred during a connection to ... SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
When I visit the http:// of my domain (with the port added) It works. But I only want the https to be available. Does anybody have any idea? Or maybe making Immich publicly available is not a good decision, but what is the alternative if I want to share pictures with family? Thank you Schoof
No description
No description
7 Replies
Immich
Immich6d ago
:wave: Hey @Schoof, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time). 2. :blue_square: read applicable release notes. 3. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed.
Zeus
Zeus6d ago
You haven’t forwarded port 443 to NPM
Schoof
SchoofOP6d ago
It also needs to be forwarded to npm?
Zeus
Zeus6d ago
If you want to use https how else would you do it?
Schoof
SchoofOP6d ago
So you're saying I need to port forward as follows: Original Port: 443, Forward to addres: 192.168.2.100, Forward to port: port NPM is running it? Which i think is 81 or something by default That to me sounds like it would just make npm publicly available But I really don't know enough about any of this 😅
Finn
Finn6d ago
You have to map 443 to 443, which is already exposed on your docker container 80(http)/443(https) are for your applications, 81(http) for the npm admin interface
Schoof
SchoofOP6d ago
I will try that, thanks That works, thanks so much! Now I'm trying the mobile app, but I can't seem to be able to upload pictures. When I go to Library, and upload a picture there it says added to queue. But nothing happens, when I check the logs I see multiple warnings: Error validation access token from server: FormatException: Unexpected character (at character 1) <html> ^ This happens only when I am locally connected to the immich server, which is through http. When I connect through my 4G (through https) it seems to work.

Did you find this page helpful?