Lemmy Support @lemmy.ml interdimensionalmeme @lemmy.ml 4d ago

"Set Up Site Administrator" problem "Toastify is awesome!" ?

Hi,

Just booted up lemmy-ui instance for the first time

It asks for "Set Up Site Administrator"

But as you can see when I press signup, nothing really happens

If I try to login with that account it says "Toastify is awesome!"

When I check the logs I get

root@storage:~# docker ps
CONTAINER ID   IMAGE                                   COMMAND                  CREATED          STATUS                    PORTS                NAMES
888bfbdd1e18   dessalines/lemmy-ui:0.19.7              "docker-entrypoint.s…"   21 minutes ago   Up 20 minutes (healthy)   1234/tcp             lemmy-lemmy-ui-1
f60bba3c14ae   dessalines/lemmy:0.19.7                 "lemmy_server"           21 minutes ago   Up 20 minutes             8536/tcp             lemmy-lemmy-1
2669e16088ca   pgautoupgrade/pgautoupgrade:17-alpine   "/usr/local/bin/dock…"   21 minutes ago   Up 20 minutes (healthy)   5432/tcp             lemmy-postgres-1
f8bf46b02c08   mwader/postfix-relay                    "/root/run"              21 minutes ago   Up 20 minutes             25/tcp               lemmy-postfix-1
de4ad69c761e   asonix/pictrs:0.5.16                    "/sbin/tini -- /usr/…"   21 minutes ago   Up 20 minutes             6669/tcp, 8080/tcp   lemmy-pictrs-1
root@storage:~# docker logs lemmy-lemmy-1
Lemmy v0.19.7
Federation enabled, host is lemmy.example.ca
Starting HTTP server at 0.0.0.0:8536
root@storage:~# docker logs lemmy-lemmy-ui-1
Lemmy-ui v0.19.7 started listening on http://0.0.0.0:1234/
31 translation imports verified.
93 date-fns imports verified.
4 highlight.js imports verified. (Only testing 4 samples.)

Not sure where to go from there ?!

You're viewing a single thread.

2 comments

Looks like an error in JavaScript is getting caught? Possibly a bad response? Look in Dev tools of your browser is what I'd do.
- Yes that was the lead.
  
  The response to POST was a 502 bad gateway
  
  This lead me to /etc/nginx/sites-available/lemmy.example.ca which has the wrong address, localhost instead of docker network
  
  specifically proxy_pass http://172.21.0.5:8536/; was pointing to 127.0.0.1
  
  location ~ ^/(api|pictrs|feeds|nodeinfo|.well-known|version|sitemap.xml) { proxy_pass http://172.21.0.5:8536/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }