Docker: Problem Joplin Server and Nginx Proxy Manager

534346346347636 · 2024-07-24T19:37:26.348Z

Operating system

Linux

Joplin version

3.0.13

Sync target

Joplin Server

What issue do you have?

I added Joplin server to my docker environment. No I want to run it behind NPM with wiki.domain.com Verything is setup in NPM, including SSL certs.
Joplin Server and and the database container are running.

But when I enter wiki.domain.com I only get 502 Bad Gateway. In Portainer I can see in the Joplin Server container logs: db: Could not connect. Will try again. getaddrinfo EAI_AGAIN db...
Any ideas?

Thanks

534346346347636 · 2024-07-26T22:59:23.264Z

Seems that Joplin Server & NPM are not popular. Noticed that for a former post, too...

dpoulton · 2024-07-27T11:23:48.698Z

Is this an NPM issue? Both containers may be running but from the brief bit of info you gave it appears that the server container cannot connect to the database container. (db: Could not connect. Will try again. getaddrinfo EAI_AGAIN db). It looks like it cannot resolve its address (DNS) and has timed out. You have truncated the error so the address may not be complete, but for some reason it appears to be trying to find an ip address for "db" (getaddrinfo EAI_AGAIN db)? Might be worth double-checking your docker-compose config.

534346346347636 · 2024-07-27T11:47:20.109Z

I used the yaml template provided on the Joplin page. Nothing changed.
Tested it before in my home network on Raspi with „db“ running perfect.

Now on a public vps server the same is not working.

534346346347636 · 2024-07-27T20:15:31.634Z

Ok got it running. I entered the IP of my database container instead of "db". Wondering why it was not working with the standard template, whre nothing was changed.

system · 2024-08-26T20:16:08.789Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.