【Bug Log】Issue of webpage not being able to open caused by Nextjs.

Dec 21, 2023#bug日志 #nomland #colib #nextjs140

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

On December 16, 2023, the website homepage (static page) suddenly stopped loading, although the internal content pages were still accessible. Some devices/browsers could open the homepage, while others were redirected to a blank page. Initially, it was thought to be a DNS contamination issue, but it was later discovered that the error was related to a 304 Not Modified response. With the help of a team member named Vico, the issue was identified and resolved by upgrading the nextjs version from 13.5.6 to 14.0.4. Since the upgrade, the problem has not reoccurred.

Date: 2023.12.16

Issue: The website homepage (static page) suddenly cannot be accessed in the evening, but the internal content pages can still be accessed. However, it is not completely inaccessible, as some devices/browsers can access it, while others are redirected to a blank page.

Resolution process:

Initially, the browser did not redirect to the about page, but instead resolved to a strange error page. So, initially, it was thought to be a DNS pollution issue. However, this issue was not replicated afterwards, and it consistently redirected to the about page.
Following the suggestion of team member @vico, we tried testing "Can we get the page HTML by using wget on the server," as follows:
```
> wget http://localhost:3000
> ...ERROR 304: Not Modified.
```
The result showed a 304 Not Modified error.
Continuing with the help of @vico, we found this issue and discovered that it was the same error. Based on the comments in the issue, we decided to upgrade the version of nextjs. Finally, we upgraded from 13.5.6 to 14.0.4, and since then, the same issue has not reoccurred.