...
Have you looked at your nginx logs to see if anything's happening and is being passed through?
Have you looked at your nginx logs to see if anything's happening and is being passed through?
nginx -t is all OK, and the logs doesn't show anything suspicious
Maybe it has something to do with the 8080 port? I am using ports 443 and 80 to host several other websites. But I've tried to change it to any other port and nothing. Maybe something about ufw rules?
Can you access Komga via the ip of your docker host on port 8080?
Can you access Komga via the ip of your docker host on port 8080?
Do you mean the IP that shows up when running docker ps? That is 0.0.0.0:8080->8080/tcp
Local IP of the LAN (like 192.168.1.35:8080) is unreachable :-(
You need to sort out the docker setup before attempting to sort your nginx setup.
What is the OS of the host running docker?
Can you post the logs of Komga also?
You need to sort out the docker setup before attempting to sort your nginx setup.
What is the OS of the host running docker?
Can you post the logs of Komga also?
Debian headless 10.6. I have another 5 containers in Docker that run flawlessly in conjunction with Nginx reverse proxy and Let's Encrypt. Can't figure out where logs are, since ~/.komga/doesn't exist.
Your docker container should output logs, try docker logs komga.
since
~/.komga/doesn't exist.
Normal, you are using Docker, you need to check here /media/externaldisk/komga/config
...
You have file permission issues in the folder you mapped to /config.
Check the permissions of /media/externaldisk/komga/config, user 1000 should have all rights to create files in that folder.
It works! 馃憤
So nice GUI and fast response! 馃
Thank you so much, @gotson
Most helpful comment
You have file permission issues in the folder you mapped to
/config.Check the permissions of
/media/externaldisk/komga/config, user 1000 should have all rights to create files in that folder.