React+php hosting

[mohhaliim]

Website URL

(please specify the URL of the site on which you are experiencing the problem)

Error Message

(white screen only)

Other Information

(I’m trying to host my full stack app, built using PHP, graphql, MySQL and reactjs, I moved my server code, build folder content and .htaccess file inside htdocs folder ) but I get a white screen, with the correct tab title from my react app, but no content at all, what did I do wrong?

[JxstErg1]

Hi and welcome to the forum! For me the page loads, but the items don’t want to show up; so I guess it’s the GraphQL request failing. You’ll have to install a SSL certificate as the GraphQL request is done by calling it through HTTPS on your code; here’s a guide to do that:

How to get Free SSL (HTTPS) on InfinityFree

If you’re using free hosting with your own domain or a subdomain, you’ll want to make your website work over HTTPS (SSL). Fortunately, InfinityFree provides all the tools you need to make it so. If you like videos better then text guides, scroll on down to the bottom of this guide. This guide uses the control panel functions and the Free SSL Certificates tool provided by InfinityFree to get SSL up and running on your site. Step 1: Set up the domain on your hosting account The first thing to do…

Also, as for the white screen, can you please send us an URL with the faulty page so we can debug it better? If you don’t do that I’ll be forced to send these articles as well, as a white screen is a symptom of a HTTP ERROR 500 on that page and most of these errors are solved by also checking the MySQL connection details:

Http error 500

When trying to access your website, you may see a page which returns the status code “500”. In Google Chrome, you’ll see a page with the error code HTTP ERROR 500. There are typically two reasons which can cause this error: The PHP code has crashed. The .htaccess file contains invalid rules. Here are some things you can try to debug and fix this. Fixing crashing PHP code A HTTP ERROR 500 simply tells you that the PHP code has crashed, but gives no information as to why it has crashed. Gett…

Common MySQL Connection Errors

Many websites use MySQL databases to store information and settings. However, there are some reasons why the connection to the database may fail. This article describes some commonly seen error messages when connecting to a database, as well as some general tips to keep in mind when setting up a database connection. Common Error Messages Using MySQL is great, but the error message returned if there is an issue logging in to your database can be quite confusing. Here are some commonly seen error…

[mohhaliim]

hey, thank you for the response, i fixed the white screen right after I created this post, it was matter of htaccess and moving the files around, but I got it to work, currently I’m struggling with the grahpql, since some queries work and the others just don’t although the difference between them is just an id value, which is super weird tbh

[mohhaliim]

i found out that my problem might be a database issue related to the version locally I’m running 8.0 but the server is running 10.6.19-MariaDB, when I tried to migrate my dump into the database I got an error regarding utf8mb4 COLLATE utf8mb4_0900_ai_ci, and I have some fields with escaping codes and HTML, is their any way to upgrade the database version? on free tier

[Greenreader9]

No, it’s not possible to change the database version on free hosting.

[Admin]

@mohhaliim

when I tried to migrate my dump into the database I got an error regarding utf8mb4 COLLATE utf8mb4_0900_ai_ci

Can you please share the exact error you got? And even better: could you share the specific statement from the database dump that triggered this error?

MariaDB 10.6 should be functionally equivalent to MySQL 8.0, but it’s not exactly the same. I doubt upgrading or downgrading MariaDB is the solution here, but it’s hard to tell because I don’t quite know the exact issue.

[mohhaliim]

i’ve fixed the issue by creating methods that handle the data encoding into json before sending them to frontend, and now it works well, thank you for your concern, you can mark this ticket as resolved.