Hello there

[kurulumuNet]

@phenomlab

the css affecting this button needs love

[phenomlab]

@kurulumu-net Thanks. I’ll fix that.

[phenomlab]

@kurulumu-net said in Hello there:

the css affecting this button needs love

Fixed in both light and dark modes.

[kurulumuNet]

@phenomlab I’m wondering what plugins you are using on sudonix.com. Can you share a list?

[phenomlab]

@kurulumu-net Of course

Active plugins:
        * nodebb-plugin-2factor@2.9.7 (installed, enabled)
        * nodebb-plugin-blog-comments@0.7.0 (installed, enabled)
        * nodebb-plugin-browsing-users@2.0.0 (installed, enabled)
        * nodebb-plugin-cards@0.2.3 (installed, enabled)
        * nodebb-plugin-category-notifications@3.0.5 (installed, enabled)
        * nodebb-plugin-composer-default@7.0.14 (installed, enabled)
        * nodebb-plugin-custom-pages@1.3.1 (installed, enabled)
        * nodebb-plugin-customize@2.0.2 (installed, enabled)
        * nodebb-plugin-dbsearch@5.1.0 (installed, enabled)
        * nodebb-plugin-desktop-notifications@0.3.3 (installed, enabled)
        * nodebb-plugin-embed@3.0.19 (installed, enabled)
        * nodebb-plugin-emoji@3.5.3 (installed, enabled)
        * nodebb-plugin-emoji-android@2.0.5 (installed, enabled)
        * nodebb-plugin-emoji-apple@2.0.5 (installed, enabled)
        * nodebb-plugin-featured-topics-extended@0.5.4 (installed, enabled)
        * nodebb-plugin-gdpr@1.0.12 (installed, enabled)
        * nodebb-plugin-glossary@0.0.10 (installed, enabled)
        * nodebb-plugin-gravatar@2.3.0 (installed, enabled)
        * nodebb-plugin-iframely@0.7.14 (installed, enabled)
        * nodebb-plugin-insult-filter@1.0.2 (installed, enabled)
        * nodebb-plugin-markdown@8.14.4 (installed, enabled)
        * nodebb-plugin-mentions@3.0.2 (installed, enabled)
        * nodebb-plugin-night-mode@1.0.7 (installed, disabled)
        * nodebb-plugin-poll@2.0.2 (installed, enabled)
        * nodebb-plugin-question-and-answer@0.12.10 (installed, enabled)
        * nodebb-plugin-recent-cards@2.0.19 (installed, enabled)
        * nodebb-plugin-reputation-rules@1.2.3 (installed, enabled)
        * nodebb-plugin-soundpack-default@2.0.0 (installed, enabled)
        * nodebb-plugin-spam-be-gone@0.7.11 (installed, enabled)
        * nodebb-plugin-sso-google@2.5.5 (installed, enabled)
        * nodebb-plugin-sso-twitter@2.5.12 (installed, enabled)
        * nodebb-plugin-twitter-netdata@1.0.0 (installed, enabled)
        * nodebb-plugin-user-level@0.4.3 (installed, enabled)
        * nodebb-plugin-write-api@5.8.10 (installed, enabled)
        * nodebb-rewards-essentials@0.2.0 (installed, enabled)
        * nodebb-theme-lavender@5.3.1 (installed, disabled)
        * nodebb-theme-material@2.13.1 (installed, disabled)
        * nodebb-theme-persona@11.2.21 (installed, enabled)
        * nodebb-theme-slick@1.4.16 (installed, disabled)
        * nodebb-theme-vanilla@12.1.9 (installed, disabled)
        * nodebb-widget-board-stats@1.2.3 (installed, enabled)
        * nodebb-widget-essentials@5.0.4 (installed, enabled)
        * nodebb-widget-html-extended@0.1.2 (installed, enabled)

[kurulumuNet]

@phenomlab Is this NodeBB default feature? The keyboard icon appears when you start typing.

[phenomlab]

@kurulumu-net Yes, that’s a feature of socket support.

[kurulumuNet]

@phenomlab I can’t see it on my site. apparently there is something wrong. It’s interesting that it doesn’t even show the people who are on the topic page at the moment.

[phenomlab]

@kurulumu-net Are you using Cloudflare ?

[kurulumuNet]

@phenomlab Yes

[phenomlab]

@kurulumu-net Known issue

Reroute socket.io | Cloudflare

@Kowlin said: I'm not experienced with nxing, but what I do know is that the subdomain you're trying to use for the websockets cannot be CloudFlare e...(more)

NodeBB Community

[kurulumuNet]

@phenomlab I think this is not the solution. Cloudflare currently supports websocket on the free plan. Websocket works, but as I said, the contacts on the topic page are not visible.

[phenomlab]

@kurulumu-net Don’t be so sure. If the native sockets does not work, it’ll fall back to XMLHTTP but that also means push won’t work as intended - including the keyboard typing indicator.

Is there anything being reported in the console, and can you share your nginx.conf file ?

EDIT - I see this on your site in the console

100% Cloudflare issue. Disable it, and I bet it works

nginx + cloudlflare = socket.io 502 errors?!

Im running NodeBB 1.17.1 and nginx/1.19.6 on the same machine as proxy. The whole machine is behind cloudflare. everything works beside a little prob...(more)

NodeBB Community

Here’s a workaround

[FAQ] Websockets not working due to misconfigured origins

This FAQ is applicable for the following situations: You're receiving the following error in the Javascript console: WebSocket connection to 'wss://...(more)

NodeBB Community

[kurulumuNet]

@phenomlab my nginx.conf;

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
	
	add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
	
	ssl_certificate /etc/ssl/kurcert.pem;
    ssl_certificate_key /etc/ssl/kurkey.pem;
	ssl_client_certificate /etc/ssl/cloudflare.crt;
 
    server_name www.kurulumu.net;
    
    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";
    }
	location /ads.txt {
     root /home/nodes/nodebb/public/;
}
	
		
}
 
server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
	
	add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
	
	ssl_certificate /etc/ssl/kurcert.pem;
    ssl_certificate_key /etc/ssl/kurkey.pem;
	ssl_client_certificate /etc/ssl/cloudflare.crt;
    
	server_name kurulumu.net;
	return 301 https://www.kurulumu.net$request_uri;
}
server {
    listen 80;
    listen [::]:80;
	   
    server_name kurulumu.net www.kurulumu.net;
	return 301 https://www.kurulumu.net$request_uri;
}

[phenomlab]

@kurulumu-net Looks good. Try disabling CF and let me know the result.

[kurulumuNet]

@phenomlab now CF is disabled. Do you still see websocket error in console? I couldn’t see the error you see in my browser when CF was enabled.

[phenomlab]

@kurulumu-net I can’t see it now, no.

[phenomlab]

@kurulumu-net any developments ?

[kurulumuNet]

@phenomlab Unfortunately not. Could I have changed a setting related to this in admin cp? I was using FullStrick SSL in CF. I installed Lets E. SSL in case it’s related to this, but the result is the same.

[phenomlab]

@kurulumu-net have you restarted NodeBB ? Let’s try that first.