Next.js: 500 Internal Server Error on GET request

[thomasbrown6]

Bug report

Describe the bug

I'm working on a website for a client. When the page first loads, it works fine with no errors. When I click to a different page from the navbar then I get a 500 Internal Server error in the browser console, on the url route I requested to GET. Despite the error in the console, the browser shows as if it's working fine. Then when I refresh the page on that specific url, I get the 500 Internal Server error page in the browser. Also, when I right click on the page to view the page source, it shows a 500 Internal Server error in HTML format. It is also good to note that this only occurs on the deployed version.

To Reproduce

Go to my client's site: http://ebonymenblackmalestrippers.com

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to the site.
2. Click on "The Men" tab and look in the browser console and you will see the error. Also if you look in the network tab of the console you will see it there as well. When you refresh the page you'll see the browser display the error.

Expected behavior

To not receive any errors, to click through the tabs perfectly fine.

Screenshots

System information

• Windows
• Browser: Chrome

Additional context

I'm using link/next to switch between pages.

Add any other context about the problem here.

[timneutkens]

Looks like the 500 is coming from your webserver and not Next.js.

[thomasbrown6]

But the thing is, I’m not using a custom server. Do I need one for this? The site doesn’t have a database. I thought next has its own built in server.

[timneutkens]

What I'm saying is you're hosting the Next.js app on a server and that server is showing a 500, this is not related to Next.js, I'm guessing the error message is coming from Apache.

[thomasbrown6]

Oh ok I understand. My question for you now is with a problem such as this, shall it be fixed if I use a custom express server? Since the 500 error is being caused by the routes and not any external resource. It seems like if I define the routes within the express server that it would work or be at least progress. What do you think?

On Sep 18, 2018, at 7:32 AM, Tim Neutkens [e-mail] wrote:

What I'm saying is you're hosting the Next.js app on a server and that server is showing a 500, this is not related to Next.js, I'm guessing the error message is coming from Apache.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[thomasbrown6]

I actually figured it out. I'm using next export and didn't define each path in my next.config.js, I only had my index file defined.

[timneutkens]

👍

[jankoboz]

I actually figured it out. I'm using next export and didn't define each path in my next.config.js, I only had my index file defined.

ebonymenblackmalestrippers.com Lol. Seems like you are building some fun websites mate!

[thomasbrown6]

Lmbo definitely wasn’t ideal

On Dec 10, 2018, at 8:40 AM, Cihangir Bozdogan [e-mail] wrote:

I actually figured it out. I'm using next export and didn't define each path in my next.config.js, I only had my index file defined.

ebonymenblackmalestrippers.com Lol. Seems like you are building some fun websites mate!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[yashualaoda]

i get the same problem .how to deal with it

[thomasbrown6]

In the next.js config file, you must define every path of every page on
your website. Next has a newer version that has a fancy way of doing this
for you.

On Wed, Jun 26, 2019 at 12:09 AM yashualaoda [e-mail]
wrote:

i get the same problem .how to deal with it

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/next.js/issues/5195?email_source=notifications&email_token=AJFSHB25NPUNQ3G62ZLD3E3P4LTW7A5CNFSM4FVUTIJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYSIJXY#issuecomment-505709791,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJFSHB6D3SQBGBAIEROFZU3P4LTW7ANCNFSM4FVUTIJQ
.

[manuel114]

Hey @thomasbrown6 is there any way you could show me an example? I have a problem by which if I click on a link (navigate through the front-end) it looks for a page on _next/static/c1gYqICa1M6k925m7QfcC/pages/sources.js, whereas if I refresh on the deployed version it just looks for it in /sources and fails with an error 500.

[TCashion]

Hey @thomasbrown6, just wondering if you could share your final solution here as I'm running into the same issue. Thanks!

[TCashion]

Hey @thomasbrown6 is there any way you could show me an example? I have a problem by which if I click on a link (navigate through the front-end) it looks for a page on _next/static/c1gYqICa1M6k925m7QfcC/pages/sources.js, whereas if I refresh on the deployed version it just looks for it in /sources and fails with an error 500.

@manuel114 did you end up finding a solution to this? I am hitting the same error.