[BUG]: Cannot contact server after installation

[sxwsxwsxwsxw]

Describe the bug

Hi,

I'd very much like to get going with Jotty, but cannot access the server after installation. I've created the docker compose file, created all the directories with the correct ownership. I've even checked if this user can access / write all the directories, all seems correct.

However, after docker compose creates the container, it notifies me that the server is ready and running at port 3000, which is of course the docker-internal port. When I then try to reach the server with a web browser, either on the internal port or the defined external port (I've done 41122:3000), my browser always says "the connection was reset".

I can see that the process is running (node server.js) with the correct user. Netstat also shows me, that the port was opened on 41122. But I cannot reach the port with a web browser. Even if I try to telnet to the port (telnet localhost 41122) the connection gets opened but then closed immediately again.

Any help would be appreciated.

Kind regards

  jotty:
    image: ghcr.io/fccview/jotty:latest
    container_name: jotty
    user: "802:802"
    ports:
      - "41122:3000"
    volumes:
      - /var/lib/jotty/data:/app/data:rw
      - /etc/jotty:/app/config:rw
      - /var/lib/jotty/cache:/app/.next/cache:rw
    restart: unless-stopped
    environment:
      - NODE_ENV=production

Steps to Reproduce

I've created the docker compose file, created all the directories with the correct ownership. I've even checked if this user can access / write all the directories, all seems correct.

How do you run Jotty?

Docker

Jotty Version

Latest

Checklist

• I have searched across other issues to make sure this bug has not been already reported.

[fccview]

Hey
Do you have any logs in your jotty docker container?

Hopefully it'll give us some insight on why this is happening ♥️

[sxwsxwsxwsxw]

Hi!

Thank you for the answer. I did not think of using a terminal to get into the container to check for logs. Could you tell me in which directory within the container the logging takes place? Then I will check today.

Kind regards

[fccview]

Hey,
If you go to the directory where your docker-compose.yml is sitting and then type docker compose logs -f it'll show you live logs for the container and you can refresh the frontend to see if anything pops up.

You can even add a DEBUGGER variable to Jotty, check the env variables doc file in this repo with all the various options ♥️

Lemme know if you need help with anything

[sxwsxwsxwsxw]

I will check soon, give me a few minutes

[sxwsxwsxwsxw]

Well. I set DEBUGGER to "*", as it says in the manual.

services:
  jotty:
    image: ghcr.io/fccview/jotty:latest
    container_name: jotty
    user: "802:802"
    ports:
      - "41122:3000"
    volumes:
      - /var/lib/jotty/data:/app/data:rw
      - /etc/jotty:/app/config:rw
      - /var/lib/jotty/cache:/app/.next/cache:rw
    restart: unless-stopped
    environment:
      - NODE_ENV=production
      - DEBUGGER=*

But all I am getting is:

root@playa:~/jotty# docker compose logs -f
jotty  | > Ready on http://0.0.0.0:3000

Even telnetting in closes the connection immediately (zero seconds):

root@playa:~/jotty# telnet localhost 41122
Trying ::1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

Honestly, I do not know what I am doing wrong. The folder structures that I created remain completely empty. What am I missing?

[fccview]

First of all do other apps work on localhost ports in your browser?

Also I noticed you are logged in as root on your server which means the container has been ran as root but the user that has access to jotty's folders is not root, I don't think this is the issue as you'd get a permission denied error but worth noting that too.

This is most likely something on your end, the only network bug I was aware of has been fixed on the develop branch (you can switch latest to develop to see if that's the issue but I doubt it)

Sorry I'm not able to be at my laptop for a while so all I can do right now is support from my phone :)

[sxwsxwsxwsxw]

Hi. Yes, localhost is a normal thing to do for me for tests like this. I have a very simple network setup here.

I tried the develop branch, does not help.

Then I am at a loss. I will have to look for other note-taking solutions. Too bad, jotty looks great.

Kind regards

[fccview]

Hey, I think I know what's going on!

You are mapping user: 802:802 but jotty is set to use 1000:1000, so you'll need to also map UID and GID to work with that user!

If you check the env variables docs you'll find the variables to set them, change it to 802 and restart your container

PUID=802
PGID=802
UMASK=002

Hopefully this is it ♥️

[fccview]

Hey @sxwsxwsxwsxw let me know if the above solves your issue :)