Community

Socket.io takes a long time to load for me why?

Technical Support

Suggested Topics

  • nullpointerN

    Connecting to socket endpoint from a custom frontend

    Solved Technical Support
    0 Votes
    10 Posts
    616 Views
    oplik0O

    @nullpointer said in Connecting to socket endpoint from a custom frontend:

    var socket = io('https://dev-forum.domain.io', { transport: ["polling", "websocket"], path: "/socket.io/", extraHeaders: { withCredentials: true, cookie: 'express.sid=s%3Am0UuuyatTTSajjAnI5gGSukaJSHJaiKpIVhb3H7L.TW4c4vZn4blOnWV1gilF9HhMqFc9g9V7NnLLZHMAmFg; Domain=dev-forum.domain.io; Path=/; HttpOnly; SameSite=Lax', }, });

    withCredentials is not a header - it's an option that should be on the same level in the settings object as extraHeaders. It should be used instead of setting the cookie header manually in the browser - but it will only work if the browser has the cookies for the website you're connecting to and needs explicit permission from it via headers (the Access-Control-Allow-* headers).
    This should look more like this:

    var socket = io('https://dev-forum.domain.io', { transport: ["polling", "websocket"], path: "/socket.io/", withCredentials: true, });

    The reason the NodeBB test example works is that it's not ran inside a browser - NodeJS, as a server environment, has quite different security requirements than browsers and also just can't save credentials for each page (imagine what programming horror having this kind of mutable state in code would be...). I'm not sure what is your ultimate goal with this code, so that's why I mentioned the cookies as needed for server-side code.

  • S

    socket.io not found (err 404)

    Technical Support
    0 Votes
    5 Posts
    584 Views
    S

    here the main config for the vhost:

    #ATTENTION! # #DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY, #SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED. server { listen 212.227.91.81:443 ssl http2; server_name community.hypercube-evolution.de; server_name www.community.hypercube-evolution.de; server_name ipv4.community.hypercube-evolution.de; server_name "community.hypercube-evolution.de.212-227-91-81.siam-net.de"; ssl_certificate /usr/local/psa/var/certificates/scfbHTbkW; ssl_certificate_key /usr/local/psa/var/certificates/scfbHTbkW; ssl_client_certificate /usr/local/psa/var/certificates/scfLt0HmX; client_max_body_size 128m; root "/var/www/vhosts/hypercube-evolution.de/community.hypercube-evolution.de"; access_log "/var/www/vhosts/system/community.hypercube-evolution.de/logs/proxy_access_ssl_log"; error_log "/var/www/vhosts/system/community.hypercube-evolution.de/logs/proxy_error_log"; #extension letsencrypt begin location ^~ /.well-known/acme-challenge/ { root /var/www/vhosts/default/htdocs; types { } default_type text/plain; satisfy any; auth_basic off; allow all; location ~ ^/\.well-known/acme-challenge.*/\. { deny all; } } #extension letsencrypt end location / { proxy_pass https://212.227.91.81:7081; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Accel-Internal /internal-nginx-static-location; access_log off; } location /internal-nginx-static-location/ { alias /var/www/vhosts/hypercube-evolution.de/community.hypercube-evolution.de/; internal; } location ~ ^/(plesk-stat|awstats-icon|webstat|webstat-ssl|ftpstat|anon_ftpstat) { proxy_pass https://212.227.91.81:7081; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Accel-Internal /internal-nginx-static-location; access_log off; } location ~ ^/~(.+?)(/.*?\.php)(/.*)?$ { alias /var/www/vhosts/hypercube-evolution.de/web_users/$1/$2; fastcgi_split_path_info ^((?U).+\.php)(/?.+)$; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_pass "unix:///var/www/vhosts/system/community.hypercube-evolution.de/php-fpm.sock"; include /etc/nginx/fastcgi.conf; } location ~ ^/~(.+?)(/.*)?$ { proxy_pass https://212.227.91.81:7081; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Accel-Internal /internal-nginx-static-location; access_log off; } location ~ \.php(/.*)?$ { fastcgi_split_path_info ^((?U).+\.php)(/?.+)$; fastcgi_param PATH_INFO $fastcgi_path_info; fastcgi_pass "unix:///var/www/vhosts/system/community.hypercube-evolution.de/php-fpm.sock"; include /etc/nginx/fastcgi.conf; } location ~ /$ { index "index.html" "index.cgi" "index.pl" "index.php" "index.xhtml" "index.htm" "index.shtml"; } add_header X-Powered-By PleskLin; include "/var/www/vhosts/system/community.hypercube-evolution.de/conf/vhost_nginx.conf"; }

    and here the include

    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:4567; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
  • 0xA4B160

    How to Load Balance for all CPU Cores

    Technical Support
    2 Votes
    16 Posts
    1916 Views
    0xA4B160

    Yes, as nginx and node.js are single threaded apps you need to spawn multiple copies of them which match the numbers of CPU cores in order to fully use the power of your server.

    0_1527420046918_Server.png

    One nginx process acts as a controller/watchdog.

    I'm no MondoDB expert but I read that it automatically uses multi-threads for read requests but uses a single thread for write operations.

  • M

    Specify Custom Theme at install time

    Technical Support
    0 Votes
    3 Posts
    2179 Views
    M

    Thank you so much!

  • sergej-saveljevS

    Long loading pages categories

    Technical Support
    0 Votes
    1 Posts
    870 Views
    sergej-saveljevS

    I created issue on the github. Please, it is very important, for me.

    Comment on the issue:

    I've written before about long loading in the administrative panel of categories, but it is important this issue!

    If more than 1500 categories, the loading becomes unbearably long, especially on slower servers, more than 10 seconds! On a very good server, it is more than 3 seconds.

    Please, deal with it as soon as possible! I do not want to change NodeBB ipboard, phpbb or something.

    Please tell me when it will be decided?

Copyright © 2023 NodeBB | Contributors