no registration page, and endless spinning

DocTator · 1 year 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.

DocTator · 1 year ago

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'

DocTator · 1 year ago

ugh, this is getting frustrating. I ran through the installation again just to end up where I ended up in the first place. Here’s my nginx configuration as lemmy.conf … maybe you can see something I don’t…

upstream lemmy { server lemmydocker.genesis-radio.net:8536; }

upstream lemmy-ui { server lemmydocker.genesis-radio.net:1234; }

server { listen 1236; listen 8536; server_name lemmydocker.genesis-radio.net; server_tokens off;

gzip on;
gzip_types text/css application/javascript image/svg+xml;
gzip_vary on;

client_max_body_size 20M;

add_header X-Frame-Options SAMEORIGIN;
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";

location / {
    set $proxypass "http://lemmy-ui";

    if ($http_accept = "application/activity+json") {
        set $proxypass "http://lemmy";
    }
    if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"") {
        set $proxypass "http://lemmy";
    }
    if ($request_method = POST) {
        set $proxypass "http://lemmy";
    }

    proxy_pass $proxypass;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

location ~ ^/(api|pictrs|feeds|nodeinfo|.well-known) {
    proxy_pass http://lemmy;
    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;
}

} _`

I don’t care if people see urls and crap as its a test server and im gonna break it down once I get it fully working anyway. Just doing this to clear up documentation issues. lol

DocTator · 1 year ago

going to redo it with some different settings and see if it makes any difference, I’ll share once I’ve completed.

DocTator · 1 year ago

https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx.conf

had to bastardize it heavily.

DocTator · 1 year ago

I had a hell of a time getting the site to even render with those instructions. I basically took a new version of the lemmy.conf file and went error by error until I got it to display. I’ve done it 3 times now, and every time it ends up broken. I’m trying to write more accurate documentation as we speak, hence why I’m trying so hard to get a clean install from scratch.

DocTator · 1 year ago

I’ve only been doing 0.18.0

DocTator · 1 year ago

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.

DocTator · 1 year ago

I had this problem… had to kind of frankenstein a conf file together and just kind of go error by error until the thing started working.

DocTator · 1 year ago

no registration page, and endless spinning

DocTator · 1 year ago

I got it working mostly. … at least it’s rendering the UI now…

Only problem is that when you try to sign up or click on just about anything, it just spins and hangs. Not sure what that’s about.

DocTator · 1 year ago

yeah, I went by the documentation … that’s completely different from what it tells you… ugh

DocTator · 1 year ago

For formatting purposes : https://pastebin.com/dbL6HHZc

DocTator · 1 year ago

deleted by creator

DocTator · 1 year ago

I installed Lemmy from scratch, and instead of a registration screen, I’m getting that. Do you know what I might have done wrong?

DocTator · 1 year ago

ubuntu 22.04 install from scratch .. not even sure what this is

DocTator · 1 year ago

it can’t even find /usr/bin/lemmy_server to run it… maybe thats where the problem is? lol

DocTator · 1 year ago

Server was installed from scratch, but I might try a Docker run just to see if there’s any difference. PostgreSQL is up and running :

doc@lemmy:/usr/bin$ systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
     Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sat 2023-06-24 01:41:07 UTC; 23h ago
   Main PID: 25761 (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 4594)
     Memory: 0B
     CGroup: /system.slice/postgresql.service

Jun 24 01:41:07 lemmy systemd[1]: Starting PostgreSQL RDBMS...
Jun 24 01:41:07 lemmy systemd[1]: Finished PostgreSQL RDBMS.
doc@lemmy:/usr/bin$

DocTator · 1 year ago

doc@lemmy:~$ journalctl -f -u lemmy.service
-- Logs begin at Sat 2023-06-24 01:25:51 UTC. --
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Main process exited, code=exited, status=203/EXEC
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Scheduled restart job, restart counter is at 5.
Jun 24 03:03:26 lemmy systemd[1]: Stopped Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:26 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:26 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Start request repeated too quickly.
Jun 24 03:03:27 lemmy systemd[1]: lemmy.service: Failed with result 'exit-code'.
Jun 24 03:03:27 lemmy systemd[1]: Failed to start Lemmy - A link aggregator for the fediverse.

DocTator · 1 year ago

Main PID: 45485 (code=exited, status=203/EXEC)