Topic: Website won't load in primary ibay, blank homepage

[smeghead]

Howdy all

I've just migrated a friend from a very old v8.2 SME to a 10.1.

Their old server had a very old flash based webite that I've copied in it's entirety to the 10.1 server .. it was fully contained in the html folder.

When I connect to the homepage I just get a blank page; if I reinstate the orig index.html file that loads fine.  This behavior is consistent if using a different ibay other than the primary.

I suspected that the httpd.conf file didn't know to use an index.php file but the templates are there & the httpd.conf file  in the /etc/httpd/conf folder has the following lines:

# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index.  Separate multiple entries with spaces.

DirectoryIndex index.htm index.html index.shtml index.cgi

DirectoryIndex index.htm index.html index.shtml index.cgi index.php index.phtml

.. and ..

#------------------------------------------------------------
# Primary ibay directories (Primary i-bay)
#------------------------------------------------------------

<Directory /home/e-smith/files/ibays/Primary/html>
    Options None
    Options +Indexes
    Options +Includes
    AllowOverride None
    Require all granted
</Directory>

<Directory /home/e-smith/files/ibays/Primary/cgi-bin>
    Options ExecCGI
    AllowOverride None
    Require all granted
</Directory>

<Directory /home/e-smith/files/ibays/Primary/files>
    AllowOverride None
    Require all granted
</Directory>

I did ponder if the multiple directoryindex lines were the issue as if the system find the first one without the php info does it also read the line with the php info.

So, what am I missing, hopefully something simple but if not I'm happy post a bug report.

Cheers

[bunkobugsy]

What says httpd error log?

[smeghead]

What says httpd error log?

No errors anywhere in any logs related to this issue.

I've checked messages, plus httpd access & error logs

Also tried explcitly nominating the index.php file in the browser, that doesn't work either.

It seems like execution of dynamic content isn't enabled when I know it is.

Hold the phone, looks like I missed a coupla entries in the error log, tho they're prob phishing attempts the entries shed a bit more light:

[cgi:error] [pid 6056] [client 193.118.53.194:56852] script not found or unable to stat: /home/e-smith/files/ibays/Primary/cgi-bin/config.exp

.. and..

[cgi:error] [pid 29096] [client 178.72.75.12:8869] Options ExecCGI is off in this directory: /home/e-smith/files/ibays/Primary/html/setup.cgi

I always thought CGI scripting was on by default, meh, loading the website into a test ibay & explcitly turning CGI on doesn't allow the index.php to run either.

Sugestions on what to look into welcome.

[brianr]

Is your SME10 up to date?

There has been some changes to the http.conf since the original SME10 to accomodate Apache 2.4.

Make sure a `yum update` does not have anything to do, and as a check, do a `signal-event post-upgrade; signal-event reboot` anyway.

[smeghead]

Is your SME10 up to date?

There has been some changes to the http.conf since the original SME10 to accomodate Apache 2.4.

Make sure a `yum update` does not have anything to do, and as a check, do a `signal-event post-upgrade; signal-event reboot` anyway.

Fully yum'd to 10.1 as of the 7th Oct

[Jean-Philippe Pialasse]

your friend SME8 was running on a very old php 5.3.3.
This is not available anymore on SME10. Older available is 5.4.16 and even that might not be able to run some older command.

by default SME runs php74, which is about to get EOL.

you should see php errors in

Code: [Select]

tail -f /var/log/php/Primary/error.log
Ideally, you should update the website to use php80 or higher, and discard Flash which has been EOL on January 12, 2021.
However if you really need a transition, install smeserver-webhosting and set your Primary ibay on php 5.4... this is the closest you can be from having this old script to run....

also if you have httaccess, they won't work with newest httpd 2.4 access rules. The result could either one could see something the httaccess was preventing or the opposite. Please review all of them  in every subdir.

Same thing for any template custom for httpd.