Frontend has white (blank) screen without errors anywhere

Terence_Hinrichsen 2020-10-08 08:24:00 UTC #1

Keywords: Magento - Microsoft Azure - Technical issue - Other
bnsupport ID: 8975f969-fd30-4ca7-a25c-3c75a147fcff
Description:
The following actions led me to this point:

Create brand new image on Azure for Magento 2.4
Install and force HTTPS
Restore mySql database from previous server.
-- Up to this point everything was still working fine.
-- Using the "Magento blank" theme as my old theme is no longer compatible with Magento 2.4
Migrate pub directory from old server (Magento 2.2)

In the admin site everything looks good, I can see my products etc.
I checked Apache log (from /opt/bitnami/apache2/logs/error_log) and cannot find a reason for the blank white screen.
I have tried to enable "display_error", but that also does not seem to work.

I cannot see what the reason for the whitescreen is so cannot start to correct the issue. I have tried all the troubleshooting steps in the documentation without luck. Also disabled varnish, no luck.

I have run the support tool for some assistance in resolving the issue or any advise on what could be causing the frontend not to load.

8975f969-fd30-4ca7-a25c-3c75a147fcff

Terence_Hinrichsen 2020-10-08 08:55:59 UTC #2

Something else I have picked up during my troubleshooting:

On the blank page, when I inspect the HTML i see a script tag which looks like this:


var BASE_URL = 'https\u003A\u002F\u002Fdomain.com\u002F';
var require = {
    'baseUrl': 'https\u003A\u002F\u002Fdomain.coma\u002Fpub\u002Fstatic\u002Fversion1602146120\u002Ffrontend\u002FMagento\u002Fblank\u002Fen_GB'
};

I would expect it to show the proper URL as in https://domain.com/
Could this be the cause and how would I go about fixing it?

amoreno 2020-10-09 13:46:26 UTC #3

Hi, @Terence_Hinrichsen.

Something else I have picked up during my troubleshooting:

On the blank page, when I inspect the HTML i see a script tag which looks like this:
var BASE_URL = 'https\u003A\u002F\u002Fdomain.com\u002F';
var require = {
   'baseUrl': 'https\u003A\u002F\u002Fdomain.coma\u002Fpub\u002Fstatic\u002Fversion1602146120\u002Ffrontend\u002FMagento\u002Fblank\u002Fen_GB'
};
I would expect it to show the proper URL as in https://domain.com/
Could this be the cause and how would I go about fixing it?

No, this is fine. Magento escapes characters there.

Can you check if this fixes your issue? https://community.bitnami.com/t/indexer-are-invalid-and-there-is-no-configuration-settings/84382/6

We have had some reports of errors in Magento that were fixed after doing that, so maybe it's also your case.

Regards,
Alejandro

Terence_Hinrichsen 2020-10-12 06:19:15 UTC #4

Thank you for the link. My search engine was already on Elasticsearch 7.0, but I modified it and saved again.
Also, I reindexed and successfully rebuilt all the indexes without any errors, so I suspect my issue is not caused by invalid indexes.
Any other advice?

amoreno 2020-10-13 08:34:29 UTC #5

There's this error in your /opt/bitnami/apps/magento/htdocs/var/log/system.log file:

[2020-10-08 08:22:02] main.ERROR: There are no commands defined in the "setup:cron" namespace.

I don't know if this has something to do, but is it possible that you have some cron jobs from your old server that are not compatible anymore? It looks like Magento has deprecated that setup:cron command.

Terence_Hinrichsen 2020-10-16 08:14:08 UTC #6

I feel really silly to have to ask, but I cannot seem to find where those cron jobs are.
Running crontab -l on the bitnami user root returns > no crontab for bitnami <
running crontab -e also wants me to creat a new editor, so not sure if I am supposed to be doing that.

I went into /etc/crontab and found a few jobs there, so I commented them out and then restarted all the services, cleared the cache and rebuilt indexes. Unfortunately the homepage is still blank.
HOWEVER, I have come across something else, if I go to a URL which is not valid I get the 404 page and on that page my advanced search seems to work.
It seems that only my landing page is broken, is there any references to the homepage stored in the database which might have broken references to the old 'theme'?

Terence_Hinrichsen 2020-10-16 08:29:40 UTC #7

I restarted the machine, cleared out the system.log file you referred to in your previous response.

I now see this error in the /opt/bitnami/apps/magento/htdocs/var/log/system.log

[2020-10-16 08:19:33] main.ERROR: No host configured to connect

amoreno 2020-10-19 10:10:13 UTC #8

Honestly, I don't know, @Terence_Hinrichsen. I would try to ask in the Magento Community in case anyone can shed some light on this (https://community.magento.com/). Since what we do is to package already existing software, we can only ask either questions related to our configuration or those that are very common or basic. In the Magento Community you should be able to find people with more expertise in the application.

Regards,
Alejandro

Terence_Hinrichsen 2020-10-23 07:46:14 UTC #9

Thank you for your help and advise amereno.
I finally found the problem and cannot believe how stupid it was.

In the previous theme, the landing page was set to a page created by the theme. This landing page had some code elements which were not compatible with Magento 2.4, so the site was working perfectly, but the landing page was blank.

it is fixed now!

amoreno 2020-10-23 13:12:47 UTC #10

I'm happy to hear that, @Terence_Hinrichsen! Please, don't hesitate to open a new thread should you encounter further issues.

Regards,
Alejandro

amoreno 2020-10-23 13:12:58 UTC #11

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!