I am trying to get Joplin server going on Linux Mint. And while I have got docker installed, the image pulled, and the container going I can't access the admin controls.
docker ps -a does show it as installed and running. But when I put in into a browser http://192.168.1.105:22300 it never connects. This is only intended on my own network not exposed to the internet. This is running in a virtual machine by the way, but I have had other apps connect fine to it without a issue (gftp for example).
I am sure I am missing something but not sure what.
Yes, I just tried http://192.168.1.105:22300/api/ping and still nothing. It just refuses/times out. This is even from inside the VM using Firefox as the browser.
What infomration do you become, if you start your container with docker compose up ?
Are there any usefull hints for a failure?
With docker -a you can see wich containers are running but if in this container is a failure that is not stopping the container, it looks like everything is running.
Mybe you could jump into the container bash without restarting via docker compose up if you use docker exec -it CONTAINER_NAME_ODER_ID bash
The container id is shown under docker ps -a
Maybe we find a hint there. It could be a problem with the user permissions of the database folder under ./data/postgres. Is the folder there and are files in it?
when I do docker compose up -d I get:
Network joplin default created
container joplin-1 started
container joplin-app-1 started
SO they do appear to be running.
docker ps -a also shows them running.
I did some searching last night and came up with the idea to use http://localhost:22300 THIS actually allowed me to get to the Joplin setup page when accessed inside the VM via the installed firefox web browser. Proof that it was working and set up. But of course this address won't extend outside the VM itself.
I have been wondering about a firewall right from the start, but I couldn't see any ports that were being blocked. A little more searching tonight and I found I forgot to configure the network port forwarding settings in the VM settings. Ooops. I had a feeling I was missing something simple and I was right. Changing the address back to http://192.168.1.105:22300 in the docker compose file, docker compose down, docker compose up -d so it would read the updates, powering down the virtual machine, then setting the port to forwarding for 22300 in the Virtual Machine networking settings, powered it back up, and it started working. All clients can see and now connect on my LAN!
Update:
I realize now I may not have been specific enough for it to help another person if they are having this issue and are looking for the settings. In my case it was the VirtualBox settings for that Virtual machine in network then (usually the first network tab) port forwarding button at the bottom. Click that then put 22300 (or the port you are using) in both for host port and guest port. Leave the other settings blank.