Cumulus Support

Hi,

I have just setup my RPi to be a local webserver and everything works fine except for my Top 10 page. It returns a 500 Internal Server Error. The specific error refers to "crbug/1173575, non-JS module files deprecated - VM9:2762".
Researching the bug tells me it relates to non-Chrome OS running Chromium but I can't seem to find a solution. I confirmed this by loading up another computer with Ubuntu webserver running Firefox and the page loads without any issues.

My system is a standard Raspian OS which many of you would have the same so I am hoping someone else may have come across this issue and worked out a solution. I am using Mark's supplied Top 10 files script with no modifications.

Regards,
Trevor

The crbug bit is just a warning, so your page should continue to work. Your error is with PHP itself. Look in your web server error log for clues.

Hi Freddie,

It's not just a warning. The page only loads the html content and doesn't load anything from the php call. If I load the php content file directly I get the below - Regards,
Trevor

Silly question, but as it is obviously your own server providing the pages have you installed PHP and checked it is working OK?

It's not a silly question but, yes, it is installed and working. I have also loaded the third party script "SQL dayfile Data Viewer" by Kocher and it is working fine.

flort wrote: ↑Tue 01 Feb 2022 9:12 am Hi Freddie,

It's not just a warning. The page only loads the html content and doesn't load anything from the php call. If I load the php content file directly I get the below -
error.jpg
Regards,
Trevor

So have you looked in your server error log?

Hi Freddie,

I'm new to setting up a webserver so thanks for pointing me in the direction of server error log. It revealed there was an issue in the database login credentials. I was missing a ' in a critical spot. All is now working fine.

Thanks again for your help.

Regards,
Trevor

flort wrote: ↑Tue 01 Feb 2022 10:36 am Hi Freddie,

I'm new to setting up a webserver so thanks for pointing me in the direction of server error log. It revealed there was an issue in the database login credentials. I was missing a ' in a critical spot. All is now working fine.

Thanks again for your help.

Regards,
Trevor

No problem. Glad you managed to get to the root of the problem.