Error while fetching page. Duplicate entry detected. Reload the page to try again.

[athenawisdoms]

Describe the bug
After installing Wiki.js using the provided docker-compose.yml, logging in and creating the first Home post, we are faced with the page that says

Error while fetching page. Duplicate entry detected. Reload the page to try again.

To Reproduce
Steps to reproduce the behavior:

1. Create a docker-compose.yml file using the contents provided here.
2. docker-compose up -d
3. Visit localhost:3000, fill up the form and click the Install button
4. Redirected to the login screen. Enter credentials and log in.
   
5. Arrived at welcome screen. Click on Create Homepage button
   
6. Click on Markdown icon button
   
7. Click on the OK button
   
   Modal is automatically closed
   
8. Click on the Create button.
9. We now get the error page
   
10. Refreshing the page brings us back to the same error page

Expected behavior
On clicking the Create button in Step 8 above, it should show us the created page (I think, have not used Wiki.js before).

Screenshots
See above

Host Info (please complete the following information):

• OS: Docker
• Wiki.js version: 2.0.12
• Database engine: Postgres 11-alpine

Additional context
Rebuild the docker 5X, encountered the same error.

docker-compose.yml

Obtained from official docs.

version: "3"
services:

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

  wiki:
    image: requarks/wiki:2
    depends_on:
      - db
    environment:
      DB_TYPE: postgres
      DB_HOST: db
      DB_PORT: 5432
      DB_USER: wikijs
      DB_PASS: wikijsrocks
      DB_NAME: wiki
    restart: unless-stopped
    ports:
      - "80:3000"

volumes:
  db-data:

[austin1howard]

Any follow up on this @athenawisdoms ? I'm seeing the same thing

[heavenkiller2018]

yes, I have the same problem, so it is affeted so that i can't use it!

Error while fetching page. Duplicate entry detected. Reload the page to try again.

[Smankusors]

can you guys confirm the version Wiki.js 2.2.50 with fresh database is still happening?

[Phillip-Kemper]

I am running into the same issue
Any Fix so far?
For me the error happens to pages in a directory that already existed

[athenawisdoms]

Unfortunately, I am still experiencing the same issue. It's completely unusable for me. @austin1howard

Looks like it is not just me encountering this strange bug.

[MatthewScholefield]

Same, I ran into this as well.

Cannot seem to delete the page, but if I try to edit it, it actually still pulls up the saved edits.

Note: I did not use the provided docker-compose.yml (installed locally in Linux with Postgres).

[mvaldes14]

Ran into the same issue today, using docker compose. i do see that the transaction made it to postgres so i'm not sure what is it the client is complaining about, all i can tell is that the backend nodejs server responds with a 500.

[ChrWieg]

Hello,
I have the same error using postgres or mariadb with Wiki.js 2.5.191, docker-compose behind a traefik edge router.
The logs show this error:
wiki_1 | 2021-03-28T10:14:43.417Z [JOB] info: Using database driver mysql2 for mariadb [ OK ]
wiki_1 | 2021-03-28T10:14:43.444Z [JOB] error: Rendering page ID 2: [ FAILED ]
wiki_1 | 2021-03-28T10:14:43.444Z [JOB] error: connect ECONNREFUSED 172.30.0.8:3306
But: it is working with sqlite! It might be an issue with the db layer?
Is this issue on the to-do list ? I can not use wiki.js without a RDBMS.

[NGPixel]

it works with sqlite because its a file based DB, not something it connects to.

[ChrWieg]

Thanks for your reply. Do you have any idea or advice how to fix the Problem?
I've been using the official docker-compose.yml with postgres: same behavior. The connection to the database is working after installation. But it stops working properly after creating the first page. The message "Duplicate entry detected" sounds more like a duplicate primary key. I can provide logs and config files if you tell me what you need.
:-)

[lkho]

Dear all,

I've found the "Error while fetching page. Duplicate entry detected. Reload the page to try again." in the source code.
https:/Requarks/wiki/blob/f55caab359ca7715012e3f9a3b9e31f16cccf399/server/models/pages.js#L943-L950
which is a TODO.

You are seeing this error because the page is found in the database, but missing a html rendered version. One of the reason can simply because your page contains invalid HTML, which caused the renderer to crash. Watch the server logs to see if there is any render jobs failing when you save a page.

example output of a PM2 deployment (make sure you set exec_mode to fork otherwise the logs from the job worker process will not show):

$ pm2 log wiki

10|wiki  | 2021-04-11T16:58:40.560Z [JOB] info: Rendering page ID 4...
10|wiki  | 2021-04-11T16:58:42.705Z [JOB] info: Using database driver pg for postgres [ OK ]
10|wiki  | 2021-04-11T16:58:44.630Z [JOB] error: Rendering page ID 4: [ FAILED ]
10|wiki  | 2021-04-11T16:58:44.630Z [JOB] error: Cannot read property 'type' of undefined

in case you got the same render error as above, debug and inspect https:/Requarks/wiki/blob/70d4c069f8eb03eaaa67fd054f3470179a101356/server/jobs/render-page.js#L92
to show the error stack trace.

The above error can be reproduced by creating a file, and inserting an invalid html snippet:

1. create a page, with whatever path, whatever title, i.e. /en/new-page
2. choose markdown editor
3. insert a blank comment <!-- --> anywhere inside the content
4. save the page
5. watch the server logs, you will see the error Cannot read property 'type' of undefined
6. click "Close" button at the top right corner and return to the viewing mode, or delete the /e from the URL i.e. /e/en/new-page -> /en/new-page
7. you see the Oops, something went wrong... Error while fetching page. Duplicate entry detected. Reload the page to try again. error.

[a-florian-h]

I had a page that would only show it's draft version, the completed .md page was ok in the page history.
Tried creating a fresh new page with the same code and ran into the issue "Error...."
removed the comments on the original page - after seeing this post.
Now it works. Thanks!

[DavidRawling]

To add to this, it occurs for me both times I've attempted to create a new page. I'm running the latest wiki.js release as of today (2.5.201) on Debian with PG 13 and node 14.16.1. It's a brand new install, directly on the VM, but with the database (and therefore the content) restored from a working wiki.js on Windows deployment. All the existing pages seemed to work before I started digging further.

The service is configured to run as a dedicated user wikijs, but the error also occurs if I run node as root.

I've also tried:

• Rebuild Page Tree
• Rerender All Pages (runs the process with the correct number of pages - but the node server log shows the rendering error for a number of pages, but not all of them. Still trying to work out what's common to the failures but not to the successes
• Flush Pages and Assets Cache (claims success)
• Flush temporary uploads (claims success)

I am beginning to suspect a plugin or something specific to the pages which fail. In my case I know I was using MultiMarkdown tables, so those and tabs are my first suspects.

[DavidRawling]

Edit: I think I've narrowed it down to any HTML comments within a Markdown page. This seems to match @lkho's experience above except that even a comment with content will cause a failure.

In my case I'm using comments embedded in strings which would otherwise be interpreted as URLs (and which cannot be resolved from 99% of the browsers viewing the page). So it's not an insurmountable problem but it's ... "slightly annoying". If I remove all comments it works correctly; if I add an HTML comment anywhere within the markdown, I see the rendering error.

It's already logged as a bug so I've just cross-referenced this discussion into the existing bug.

[pathaksa]

I had the same issue and solved it by using an alphanumeric password for PostreSQL.

[NGPixel]

That's completely unrelated.

[daBONDi]

Created with a fresh database

2021-08-01T18:18:16.165Z [JOB] error: Rendering page ID 1: [ FAILED ]
2021-08-01T18:18:16.166Z [JOB] error: Cannot read property 'length' of null

Query with graphql shows the page

i think it have todo with permission to write the cached folder, will logging IO on linux server next

[lracicot]

I have the same problem. Just installed requarks/wiki:2 on docker swam with postgres:11-alpine.

[PythonCoderAS]

I ran into the same issue. According to @DavidRawling, I removed the HTML comments, and the page rendered perfectly. It seemed to be an error even when the comments had data.

[kunom]

Same issue here, trying to create an almost empty first page in markdown editor:

wikijs  | 2021-10-21T18:45:30.113Z [JOB] info: Rendering page ID 1...
wikijs  | 2021-10-21T18:45:35.664Z [JOB] info: Using database driver sqlite3 for sqlite [ OK ]
wikijs  | 2021-10-21T18:45:37.006Z [JOB] error: Rendering page ID 1: [ FAILED ]
wikijs  | 2021-10-21T18:45:37.010Z [JOB] error: Invalid or unexpected token
wikijs  | 2021-10-21T18:45:37.049Z [MASTER] warn: Error when running job render-page: Invalid or unexpected token

[jtjanecek]

I noticed this warning:

2021-12-14T21:12:49.688Z [MASTER] warn: EACCES: permission denied, mkdir '/home/my_user'

So I mounted a local folder to /home, and it fixed the issue for me.

I suspect that the rendering writes temporary files to /home, and the docker image doesn't have write access:

docker run --rm -d -p 443:443 --name wiki -e CONFIG_FILE=/config/config.yml -v $PWD/home:/home -v $PWD/config:/config -v $PWD/certs:/certs requarks/wiki:2.5

[veg4c0re]

I have the same problem after moving assets into new folders and then replacing the old path with the new one in the content and render columns. I'm not using docker. Is there a fix of this bug?

I wrote a Python script to do this.

[NGPixel]

Try to re-render the page (either edit + save, or re-render all pages via admin > utilities.

[veg4c0re]

I got this error Completed with 19 pages that failed to render. Check server logs for details.

The failed pages showed this:

Sep 22 08:05:10 ip-10-0-0-230 node[51003]: 2022-09-22T08:05:10.361Z [JOB] error: Rendering page ID 38: [ FAILED ]

Sep 22 08:05:10 ip-10-0-0-230 node[51003]: 2022-09-22T08:05:10.361Z [JOB] error: Input data should be a String

[veg4c0re]

Oh, content and render are NULL.

[krvns]

Seeing the same issue:
Wiki.js version: 2.5.295
Database engine: Postgres 11-alpine

Server logs:

method: 'select',
options: {},
timeout: false,
cancelOnTimeout: false,
bindings: [ 'home', 'en' ],
 __knexQueryUid: '30c1a7f9-a3fb-11ed-847d-bf',
sql: 'select "pages"."id", "pages"."path", "pages"."hash", "pages"."title", "pages"."description", "pages"."isPrivate", "pages"."isPublished", "pages"."privateNS", "pages"."publishStartDate", "pages"."publishEndDate", "pages"."content", "pages"."render", "pages"."toc", "pages"."contentType", "pages"."createdAt", "pages"."updatedAt", "pages"."editorKey", "pages"."localeCode", "pages"."authorId", "pages"."creatorId", "pages"."extra", "author"."name" as "authorName", "author"."email" as "authorEmail", "creator"."name" as "creatorName", "creator"."email" as "creatorEmail", "tags"."tag" as "tags:tag", "tags"."title" as "tags:title", "tags"."id" as "tags:id" from "pages" inner join "users" as "author" on "author"."id" = "pages"."authorId" inner join "users" as "creator" on "creator"."id" = "pages"."creatorId" left join "pageTags" as "tags_join" on "tags_join"."pageId" = "pages"."id" left join (select "tag", "title", "tags"."id" from "tags") as "tags" on "tags_join"."tagId" = "tags"."id" where "pages"."path" = ? and "pages"."localeCode" = ?'

while trying to delete 'Home" page (the only page that is there), I'm getting:

Fri, Feb 3 2023 2:46:53 pm | method: 'del',
Fri, Feb 3 2023 2:46:53 pm | options: {},
Fri, Feb 3 2023 2:46:53 pm | timeout: false,
Fri, Feb 3 2023 2:46:53 pm | cancelOnTimeout: false,
Fri, Feb 3 2023 2:46:53 pm | bindings: [ 10 ],
Fri, Feb 3 2023 2:46:53 pm | __knexQueryUid: '822c8d30-a3fb-11ed-847d-b884631ff',
Fri, Feb 3 2023 2:46:53 pm | sql: 'delete from "pages" where "id" = ?',
Fri, Feb 3 2023 2:46:53 pm | returning: undefined
Fri, Feb 3 2023 2:46:53 pm | }
Fri, Feb 3 2023 2:46:53 pm | 2023-02-03T19:46:53.937Z [MASTER] warn: Error when running job rebuild-tree:

[denhyde]

Hi. I have no problem accessing postgres DB container (172.18.0.2:5432 in the below log) from the wiki Docker container. Wiki configuration updated via the web UI is successfully saved in the DB. I disabled the comments in the wiki settings. When I tried to create the first page using Markdown, I received "Error when running job render-page: connect ECONNREFUSED 172.18.0.2:5432" in the web UI, however, the page was saved successfully:

wiki=# \c wiki
psql (12.15 (Ubuntu 12.15-0ubuntu0.20.04.1), server 11.16 (Debian 11.16-1.pgdg90+1))
You are now connected to database "wiki" as user "wiki".
wiki=# SELECT * FROM pages;

 id | path |                   hash                   |    title    | description | isPrivate | isPublished | privateNS | publishStartDate | publishEndDate |  content  | render | toc | contentType |        createdAt         |        updatedAt         | editorKey | localeCode | authorId | creatorId |       extra        
----+------+------------------------------------------+-------------+-------------+-----------+-------------+-----------+------------------+----------------+-----------+--------+-----+-------------+--------------------------+--------------------------+-----------+------------+----------+-----------+--------------------
  1 | home | b29b5d2ce62e55412776ab98f05631e0aa96597b | Exam Wiki |             | f         | t           |           |                  |                | # Welcome+|        | []  | markdown    | 2023-05-31T19:21:09.311Z | 2023-05-31T19:21:09.311Z | markdown  | en         |        1 |         1 | {"js":"","css":""}
    |      |                                          |             |             |           |             |           |                  |                |           |        |     |             |                          |                          |           |            |          |           | 
(1 row)

The wiki container log showed this despite successfully saving the first page:

2023-05-31T18:25:59.668Z [JOB] info: Rendering page ID 1...
2023-05-31T18:26:00.079Z [JOB] info: Using database driver pg for postgres [ OK ]
2023-05-31T18:26:01.100Z [JOB] error: Rendering page ID 1: [ FAILED ]
2023-05-31T18:26:01.100Z [JOB] error: connect ECONNREFUSED 172.18.0.2:5432
2023-05-31T18:26:01.118Z [MASTER] warn: Error when running job render-page: connect ECONNREFUSED 172.18.0.2:5432
2023-05-31T18:28:53.450Z [JOB] info: Rebuilding page tree...
2023-05-31T18:28:53.936Z [JOB] info: Using database driver pg for postgres [ OK ]
2023-05-31T18:28:54.956Z [JOB] error: Rebuilding page tree: [ FAILED ]
2023-05-31T18:28:54.957Z [JOB] error: connect ECONNREFUSED 172.18.0.2:5432
2023-05-31T18:28:54.962Z [MASTER] warn: Error when running job rebuild-tree: connect ECONNREFUSED 172.18.0.2:5432

Checking config.yml also confirmed that 172.18.0.2 is indeed the IP of the DB container to which I refer via the hostname which I used to create it.

When I tried to access the created page, I received this error:

Oops, something went wrong...
Page has no rendered version. Looks like the Last page render failed. Try to edit the page and save it again.

Thus, there is no problem with accessing the postgres DB, nor with saving pages, but I can't render them. I'm not sure what to do.

[NGPixel]

Make sure your DB accepts multiple connections simultaneously. The render happens on a separate process using its own connection.