Network Error: Unexpected token '<', "<html> <h"... is not valid JSON #6589
Replies: 6 comments 1 reply
-
You probably have some kind of network filter or something preventing your instance from accessing the internet. Your screenshot shows the placeholders for the translations. This is because your instance could not download any translations. Note that you can sideload the translations, if you can't enable s direct internet connection. |
Beta Was this translation helpful? Give feedback.
-
Weird connection timeouts, so I increased to 600s which seemed to work.
I'll talk with my provider to figure this out, thank you so much. :)
|
Beta Was this translation helpful? Give feedback.
-
Just saw exact same error on my side. Happens If I want to edit some pages. I'm having this docker compose running since a long time. First time I see a error like this.
Running the latest version and also seeing the problems in the Admin panel. In front to the docker I have a nginx reverse proxy running with the following config. This worked so fare for a long time.
|
Beta Was this translation helpful? Give feedback.
-
After digging some more I found this nginx error
Fast it was obvious that the misconfiguration will be found in the nginx config. Remove this section of the nginx config completely or adopt the settings till it works!
Restart the server and you should be fine. The problem with the placeholder titles in the menu bar of the admin panel could be fixed by adding
|
Beta Was this translation helpful? Give feedback.
-
github copilot said that because wikijs want a json respone but it got the html so we got this error. we can use server {
listen 443 ssl;
server_name your.website.com;
ssl_certificate /etc/letsencrypt/live/*.pem;
ssl_certificate_key /etc/letsencrypt/live/*.pem;
ssl_session_cache shared:SSL:1m;
ssl_session_timeout 5m;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
location / {
proxy_pass http://192.168.1.11:3000;
proxy_set_header Host $host;
proxy_intercept_errors off;
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 Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_cache_bypass $http_upgrade;
}
}
|
Beta Was this translation helpful? Give feedback.
-
@LucaLush thanks for your input. currently I have this working config running. server {
server_name somedomain.org;
access_log /var/log/nginx/access-docs.log;
error_log /var/log/nginx/error-docs.log;
listen 443 ssl http2;
ssl_session_cache shared:le_nginx_SSL:1m;
ssl_session_timeout 1440m;
ssl_protocols TLSv1.3;
ssl_prefer_server_ciphers on;
ssl_ciphers EECDH+AESGCM:EDH+AESGCM;
ssl_certificate /etc/letsencrypt/live/somedomain.org/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/somedomain.org/privkey.pem;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
add_header X-Content-Type-Options nosniff;
add_header X-XSS-Protection "1; mode=block";
add_header X-Robots-Tag none;
add_header X-Download-Options noopen;
add_header X-Permitted-Cross-Domain-Policies none;
add_header Referrer-Policy "same-origin" always;
add_header X-Frame-Options "SAMEORIGIN";
location / {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header REMOTE_HOST $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-FORWARDED-PROTOCOL $scheme;
proxy_pass http://127.0.0.1:3000;
}
} |
Beta Was this translation helpful? Give feedback.
-
I just installed the latest version of v2, and am getting
Network Error: Unexpected token '<', "<html> <h"... is not valid JSON
when I go to Admin to set stuff up. Everything shows as this too:Beta Was this translation helpful? Give feedback.
All reactions