Skip Navigation
Lemmy Support @lemmy.ml DocTator @lemmy.ml

no registration page, and endless spinning

lemmydocker.genesis-radio.net /

So I seem to have "successfully" set up a Lemmy from Scratch server on Ubuntu 22.04 .. The problem I'm having is it doesn't seem to go to a registration page, and when you try to sign up for a new account, or do anything really, it seems to endlessly spin. Any ideas?

12
12 comments
  • Did you look in the server logs?

    Is the problem resolved?

    • Still having the issue unfortunately ... the only evidence I can find is in /var/log/nginx/error.log .. posted snippet below :

      2023/06/28 04:34:55 [error] 25293#25293: *257 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/28 05:56:47 [crit] 25293#25293: *306 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 165.227.76.114, server: 0.0.0.0:443 2023/06/28 06:02:19 [crit] 25293#25293: *317 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 212.102.40.218, server: 0.0.0.0:443 2023/06/28 09:39:37 [crit] 25293#25293: *463 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 184.105.247.196, server: 0.0.0.0:443 2023/06/28 15:43:38 [crit] 25293#25293: *592 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 87.236.176.107, server: 0.0.0.0:443 2023/06/28 17:22:01 [error] 25293#25293: *673 connect() failed (111: Unknown error) while connecting to upstream, client: 178.150.14.250, server: lemmydocker.genesis-radio.net, request: "GET /feeds/local.xml?sort=Active HTTP/1.1", upstream: "http://45.79.157.6:8536/feeds/local.xml?sort=Active", host: "lemmydocker.genesis-radio.net" 2023/06/29 01:36:10 [crit] 25293#25293: *792 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 64.62.197.238, server: 0.0.0.0:443 2023/06/29 04:19:57 [crit] 25293#25293: *848 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 212.102.40.218, server: 0.0.0.0:443 2023/06/29 06:23:02 [crit] 25293#25293: *884 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 192.241.201.43, server: 0.0.0.0:443 2023/06/29 08:19:40 [crit] 25293#25293: *918 SSL_do_handshake() failed (SSL: error:0A00006C:SSL routines::bad key share) while SSL handshaking, client: 174.138.34.74, server: 0.0.0.0:443 2023/06/29 21:51:57 [error] 25293#25293: *1593 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:51:57 [error] 25293#25293: *1595 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:51:58 [error] 25293#25293: *1597 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:51:58 [error] 25293#25293: *1599 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:51:59 [error] 25293#25293: *1601 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:52:01 [error] 25293#25293: *1603 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:52:04 [error] 25293#25293: *1605 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:52:11 [error] 25293#25293: *1607 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:52:17 [error] 25293#25293: *1609 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net" 2023/06/29 21:52:25 [error] 25293#25293: *1611 connect() failed (111: Unknown error) while connecting to upstream, client: 24.168.40.249, server: lemmydocker.genesis-radio.net, request: "GET /api/v3/ws HTTP/1.1", upstream: "http://45.79.157.6:8536/api/v3/ws", host: "lemmydocker.genesis-radio.net"

      I'm pretty sure it's something on my end, because when I build Lemmy with the easy deploy script its fine.

  • I just set up from scratch on FreeBSD and had that issue at first as well. Turns out the instructions on the website could use some love as the ansible nginx configs were out of date. I manually updated my nginx config to match the blocks for UI and BE in the nginx_internal.conf and that seemed to resolve my registration issues.

    Also make sure you're front end version is the same as your backend. I also made that mistake.

You've viewed 12 comments.