this post was submitted on 28 Jun 2023
1 points (100.0% liked)

Lemmy Support

4651 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 6 years ago
MODERATORS
dessalines@lemmy.ml
1
no registration page, and endless spinning (lemmydocker.genesis-radio.net)
submitted 2 years ago by DocTator@lemmy.ml to c/lemmy_support@lemmy.ml
8 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] DocTator@lemmy.ml 0 points 2 years ago (1 children)

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.

[–] RoundSparrow@lemmy.ml 0 points 2 years ago (1 children)

This is 0.18.0 or 0.18.1? As this is all websocket /api/v3/ws

[–] DocTator@lemmy.ml 0 points 2 years ago (1 children)

I've only been doing 0.18.0

[–] RoundSparrow@lemmy.ml 1 points 2 years ago (1 children)

Dong from scratch, make sure your lemmy-ui github checkout was 0.18 - as those logs look like what the outdated docs say.

[–] DocTator@lemmy.ml 2 points 2 years ago (1 children)

When trying to build lemmy ui with github checkout 0.18 I get this error :

error /var/lib/lemmy-ui/node_modules/sharp: Command failed.
Exit code: 1
Command: (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
Arguments: 
Directory: /var/lib/lemmy-ui/node_modules/sharp
Output:
sharp: Installation error: EACCES: permission denied, mkdir '/home/lemmy/.npm'
sharp: Are you trying to install as a root or sudo user?
sharp: - For npm <= v6, try again with the "--unsafe-perm" flag
sharp: - For npm >= v8, the user must own the directory "npm install" is run in
sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies

Error: ENOENT: no such file or directory, open '/home/lemmy/.yarnrc'
[–] RoundSparrow@lemmy.ml 2 points 2 years ago (1 children)

looks like a file permission problem. would 1) delete the entire /var/lib/lemmy-ui tree, 2) make sure you are dong sudo -u lemmy bash and on the correct account, 3) start over at git checkout

[–] DocTator@lemmy.ml 1 points 2 years ago

tried that with the same result. It works if I git checkout 0.16.7 as stated in the docs, but every time I try to build using 0.18.0 it'll throw that file permission error.