Network Error: Unexpected token '<', "<html> <h"... is not valid JSON #6589

P1xelC0da · 2023-07-21T06:41:50Z

P1xelC0da
Jul 21, 2023

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:

P4mes4n · 2023-07-21T13:43:16Z

P4mes4n
Jul 21, 2023

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.

0 replies

P1xelC0da · 2023-07-21T22:57:02Z

P1xelC0da
Jul 21, 2023
Author

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. :)

1 reply

wreidlinger Jan 9, 2024

Thanks for your bug report! Where you able to fix the issue in the end?
Do you know in which version of wiki.js you did experienced the error?

wreidlinger · 2024-01-09T22:02:32Z

wreidlinger
Jan 9, 2024

Just saw exact same error on my side. Happens If I want to edit some pages.

From the Chrome DEV Tool:

I'm having this docker compose running since a long time. First time I see a error like this.
This is the docker compose config:

version: "3"
services:

  db:
    image: postgres:15-alpine
    environment:
      POSTGRES_DB: wiki
      POSTGRES_PASSWORD: *****
      POSTGRES_USER: wiki
    logging:
      driver: "none"
    restart: unless-stopped
    volumes:
      - db-data:/var/lib/postgresql/data

  wiki:
    image: ghcr.io/requarks/wiki:2
    depends_on:
      - db
    environment:
      DB_TYPE: postgres
      DB_HOST: db
      DB_PORT: 5432
      DB_USER: wiki
      DB_PASS: ******
      DB_NAME: wiki
    restart: unless-stopped
    ports:
      - "127.0.0.1:3000:3000"
volumes:
  db-data:

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.

/upstream docs {
  server 127.0.0.1:3000;
}

server {
  listen 80;

  if ($scheme != "https") {
      return 301 https://$host$request_uri;
  }

  listen 443 ssl;
  ssl_certificate /etc/letsencrypt/live/docs.domain.something/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/docs.domain.something/privkey.pem;

  server_name docs.domain.something;

  add_header Strict-Transport-Security "max-age=31536000; includeSubdomains; preload";

  location / {
    proxy_pass         https://docs;
    proxy_http_version 1.1;

    proxy_set_header   Upgrade $http_upgrade;
    proxy_set_header   Connection "upgrade";
    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 http;
    proxy_redirect     https:// $scheme:https://;

    proxy_set_header   Host $http_host;

    proxy_connect_timeout   1m;
    proxy_send_timeout      1m;
    proxy_read_timeout      1m;
  }
}

0 replies

wreidlinger · 2024-01-16T21:04:36Z

wreidlinger
Jan 16, 2024

After digging some more I found this nginx error 413 Request Entity Too Large

Request URL: https://docs.domainexample.net/graphql
Request Method: POST
Status Code: 413 Request Entity Too Large
Remote Address: 10.1.99.18:443
Referrer Policy: same-origin

Fast it was obvious that the misconfiguration will be found in the nginx config.
By adding / modifying the following parameters in the /etc/nginx/nginx.conf file I was able to fix the error.

Remove this section of the nginx config completely or adopt the settings till it works!

        ##buffer policy
        # https://www.digitalocean.com/community/tutorials/how-to-optimize-nginx-configuration#buffers
        client_body_buffer_size 1K;
        client_header_buffer_size 1k;
        client_max_body_size 10M;
        large_client_header_buffers 2 1k;
        ##end buffer policy

Restart the server and you should be fine.
sudo systemctl restart nginx.service

The problem with the placeholder titles in the menu bar of the admin panel could be fixed by adding SSL_ACTIVE: 0 in the docker compose file. At least it worked for me, even before I fixed the other problem with the 413 Request Entity Too Large error.

version: "3.8"
services:
  db:
    image: postgres:15-alpine
    environment:
      POSTGRES_DB: wiki
      POSTGRES_PASSWORD: wikijsrocks
      POSTGRES_USER: wiki
    logging:
      driver: "none"
    restart: unless-stopped
    volumes:
      - db-data:/var/lib/postgresql/data

  wiki:
    image: ghcr.io/requarks/wiki:2.5
    depends_on:
      - db
    environment:
      DB_TYPE: postgres
      DB_HOST: db
      DB_PORT: 5432
      DB_USER: wiki
      DB_PASS: wikijsrocks
      DB_NAME: wiki
      SSL_ACTIVE: 0

    restart: unless-stopped
    ports:
      - "127.0.0.1:3000:3000"
volumes:
  db-data:

0 replies

LucaLush · 2024-08-10T06:27:54Z

LucaLush
Aug 10, 2024

github copilot said that because wikijs want a json respone but it got the html so we got this error. we can use proxy_intercept_errors off; to disable nginx from returning html respone and let wikijs handle it. this is my nginx config. it works for me

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     https://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;
                }

        }

0 replies

wreidlinger · 2024-08-10T06:47:41Z

wreidlinger
Aug 10, 2024

@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              https://127.0.0.1:3000;
       }
}

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Network Error: Unexpected token '<', "<html> <h"... is not valid JSON #6589

{{title}}

Replies: 6 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Network Error: Unexpected token '<', "<html> <h"... is not valid JSON #6589

P1xelC0da Jul 21, 2023

Replies: 6 comments · 1 reply

P4mes4n Jul 21, 2023

P1xelC0da Jul 21, 2023 Author

wreidlinger Jan 9, 2024

wreidlinger Jan 9, 2024

wreidlinger Jan 16, 2024

LucaLush Aug 10, 2024

wreidlinger Aug 10, 2024

P1xelC0da
Jul 21, 2023

Replies: 6 comments 1 reply

P4mes4n
Jul 21, 2023

P1xelC0da
Jul 21, 2023
Author

wreidlinger
Jan 9, 2024

wreidlinger
Jan 16, 2024

LucaLush
Aug 10, 2024

wreidlinger
Aug 10, 2024