I am wanting to use the forum on my pool site. But the forum adddress is going to be https://ktiptokyng.com/forum/
-
runs fine on 192.168.1.189:4567/forum. But doesn't on ssl https://kriptokyng.com/forum
-
is this thing much faster running on redis?
-
is this thing much faster running on redis?
@kriptokyng if it's perceivably slow then no, something is wrong and it's not the database.
-
@kriptokyng fwiw that link loads fine for me
-
this happens when i try to ligin -
2025-04-29T13:51:28.170Z [4567/120129] - error: POST /forum/login?error=csrf-invalid invalid csrf token 2025-04-29T13:53:47.979Z [4567/120129] - error: POST /forum/login?error=csrf-invalid invalid csrf token 2025-04-29T13:54:38.930Z [4567/120129] - error: POST /forum/login invalid csrf token -
2025-04-29T13:51:28.170Z [4567/120129] - error: POST /forum/login?error=csrf-invalid invalid csrf token 2025-04-29T13:53:47.979Z [4567/120129] - error: POST /forum/login?error=csrf-invalid invalid csrf token 2025-04-29T13:54:38.930Z [4567/120129] - error: POST /forum/login invalid csrf token@kriptokyng what is the value of
urlinconfig.json? -
"url": "https://kriptokyng.com:4567/forum/",
-
@kriptokyng so that is wrong. Change it to match the proper url used to access the site.
-
server { root /var/www/kriptokyn/html; index index.html index.htm index.nginx-debian.html; server_name kriptokyng.com ; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:7000; # no trailing slash proxy_redirect off; } location /api/ { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4000/api/; # no trailing slash proxy_redirect off; } location /forum { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4567/forum; # no trailing slash proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } listen [::]:443 ssl ipv6only=on; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/kriptokyng.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/kriptokyng.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = kriptokyng.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; listen [::]:80; server_name kriptokyng.com ; return 404; # managed by Certbot } -
server { root /var/www/kriptokyn/html; index index.html index.htm index.nginx-debian.html; server_name kriptokyng.com ; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:7000; # no trailing slash proxy_redirect off; } location /api/ { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4000/api/; # no trailing slash proxy_redirect off; } location /forum { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4567/forum; # no trailing slash proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } listen [::]:443 ssl ipv6only=on; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/kriptokyng.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/kriptokyng.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = kriptokyng.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; listen [::]:80; server_name kriptokyng.com ; return 404; # managed by Certbot }@kriptokyng fix config.json
url. The value is wrong. -
@kriptokyng stop using
:4567in the url.
