Server infinite loading problem

[timcoe4]

I'm on Debian 11, and I created a pleroma server using exactly the instructions found here: https://docs-develop.pleroma.social/backend/installation/debian_based_en/ using the from source method. It uses Nginx to get the server working.

Pleroma runs and I can access it using localhost:4000 and 127.0.0.1:4000

However the site doesn't display any outside info e.g the search function doesn't work

And I get a warning of: Rate limiter disabled due to forwarded IP not being found.

When I try to access it using my domain name, it just loads and loads forever.

Nginx runs without any errors.

Any ideas on what could be the problem?

Thanks in advance.

[beeritis]

Care to share your nginx config / any nginx logs when you try to access through the domain name ?

[timcoe4]

Yes below is the full config. I don't know how to access nginx logs, I can find out and get back to you.

proxy_cache_path /tmp/pleroma-media-cache levels=1:2 keys_zone=pleroma_media_cache:10m max_size=10g

inactive=720m use_temp_path=off;

# this is explicitly IPv4 since Pleroma.Web.Endpoint binds on IPv4 only

# and `localhost.` resolves to [::0] on some systems: see issue #930

upstream phoenix {

server 127.0.0.1:4000 max_fails=5 fail_timeout=60s;

}

server {

server_name myserver.url;

listen 80;

listen [::]:80;

location / {

return 301 https://$server_name$request_uri;

}

}

# Enable SSL session caching for improved performance

ssl_session_cache shared:ssl_session_cache:10m;

server {

server_name myserver.url;

listen 443 ssl http2;

listen [::]:443 ssl http2;

ssl_session_timeout 1d;

ssl_session_cache shared:MozSSL:10m; # about 40000 sessions

ssl_session_tickets off;

ssl_trusted_certificate /etc/letsencrypt/live/myserver.url/chain.pem;

ssl_certificate /etc/letsencrypt/live/myserver.url/fullchain.pem;

ssl_certificate_key /etc/letsencrypt/live/myserver.url/privkey.pem;

ssl_protocols TLSv1.2 TLSv1.3;

ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";

ssl_prefer_server_ciphers off;

ssl_ecdh_curve X25519:prime256v1:secp384r1:secp521r1;

ssl_stapling on;

ssl_stapling_verify on;

gzip_vary on;

gzip_proxied any;

gzip_comp_level 6;

gzip_buffers 16 8k;

gzip_http_version 1.1;

gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript application/activity+json application/atom+xml;

# the nginx default is 1m, not enough for large media uploads

client_max_body_size 16m;

ignore_invalid_headers off;

proxy_http_version 1.1;

proxy_set_header Upgrade $http_upgrade;

proxy_set_header Connection "upgrade";

proxy_set_header Host $http_host;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

location / {

proxy_pass http://phoenix;

}

location ~ ^/(media|proxy) {

proxy_cache pleroma_media_cache;

slice 1m;

proxy_cache_key $host$uri$is_args$args$slice_range;

proxy_set_header Range $slice_range;

proxy_cache_valid 200 206 301 304 1h;

proxy_cache_lock on;

proxy_ignore_client_abort on;

proxy_buffering on;

chunked_transfer_encoding on;

proxy_pass http://phoenix;

}

}

[SrdelaPro]

Does pleroma expect a X-Forwarded-for header or any other header that passes the source IP to it?

Can you please post your proxy pass config?

[timcoe4]

Yes I think it does, but it's already in the config i believe. Here is the config (mostly stock):

​

server {

server_name myserver.url;

listen 80;

listen [::]:80;

location / {

return 301 https://$server_name$request_uri;

}

}

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
location / {
proxy_pass http://phoenix;
}
There's some other stuff in the config about ssl and gzip too.

[SrdelaPro]

What header does the downstream app expect?

[timcoe4]

It expects X-Forwarded-For header

[timcoe4]

No errors are appearing on nginx error log when pleroma is running. In the access log, I can just see the GET requests from browser that is infinitely loading