problem with sitemap
-
Everything is alright.
NodeBB running without problem, applied ssl, and did configuration for reconnecting www to non-www and config.json for nodebb(put my non-www domain example.com in it).But only problem is sitemap.
I've tried to fix this problem for 3 days but still having problem with sitemap.NodeBB is showing my sitemap at 'example.com/sitemap.xml' but google search console can't read my sitemap.
I've tried putting
https://example.com/sitemap.xml
http://example.com/sitemap.xml
https://www.example.com/sitemap.xml
http://www.example.com/sitemap.xml
but search console can't read all of them.I think something is wrong with nginx configuration or SSL applying maybe..
Cuz I did everything same as official installation guide, but did different for those.Here's my nginx default file
# Default HTTPS server configuration server { listen 443 ssl http2 default_server; listen [::]:443 ssl http2 default_server; server_name example.com; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; ssl_trusted_certificate /etc/letsencrypt/live/example.com/fullchain.pem; include /etc/nginx/snippets/ssl.conf; access_log /var/log/nginx/example.com.access.log; error_log /var/log/nginx/example.com.error.log; 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; # 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"; } location ~ /\.ht { deny all; } } # HTTPS www. server configuration server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name www.example.com; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; ssl_trusted_certificate /etc/letsencrypt/live/example.com/fullchain.pem; include /etc/nginx/snippets/ssl.conf; location / { return 301 https://example.com$request_uri; } } # Default server configuration server { listen 80; listen [::]:80 default_server; server_name example.com; include /etc/nginx/snippets/letsencrypt.conf; location / { return 301 https://example.com$request_uri; } } # HTTP - CNAME Connect www.example.com to example.com server { listen 80; listen [::]:80; server_name www.example.com; include /etc/nginx/snippets/letsencrypt.conf; location / { return 301 https://example.com$request_uri; } }
Anyone know solution, help me plz
-
@nubi-kr I don't know that much about this... but it might be your nodebb config file. It might be set to "example.com" (your URL) and will go to www.that, but maybe you need to change it to what it is when you visit it. Try putting www.yoururl.com
-
@dunlix yes
if i go to
https://example.com/sitemap.xml
then sitemap shows up, like...
https://example.com/sitemap/topic.1.xml
...this kind of things in it
i can access to all those sitemap files but google can't -
@dunlix I think it is google's problem
https://support.google.com/webmasters/thread/2790050?hl=en
just same as my case.
answer in this link saidYour sitemap can be processed by google ranging from 24 hours to 24 days (even 1 month + in some rare case)