ProAvia

Sounds like you need to double check that all "http" entries are changed to "https". There is a post in the forums that discusses changing to https - but I was unable to locate it. EDIT: Have a look at this thread.....

CURRENT_SKIN refers to the skin selected in the admin panel. If no addon skin installed, that means the crystal skin. But the crystal skin doesn't have a header.php file. I bet the old db is set for your addon skin instead of crystal. Go to admin panel and set the skin to crystal. Or if you can't get to admin panel, go into the active db Settings table and change the skin name there.

Great... let us know how it works out.

Make a backup of your database and marry that backup database to this new install. Test to see if its working. If so, add you skin and then slowly add any addon modules you use. If its still all working, change the new install to your old live database and redirect your domain to the new install location. If all that goes well, you now have a new install with your original database that is working as intended. If it doesn't work as you are doing the steps, investigate the last item you did which caused the issue to return.

Glad to help - wish we could have found the culprit. Maybe someone else will see this thread and be able to assist further. Maybe time to start thinking of an upgrade to phpVMS 7 when released. Now may be a good time to start testing it out.

OK - that's good. Can you try setting up a development site with a new install of phpVMS 5.5.2 and see if it works? Leave our live site alone for now. Run the dev site on the same host in a different directory.

I wonder if your issue has anything to do with "fastcgi"? I am not well versed enough to know. The last errors mention "fastcgi" and creating a default object in the PIREPData.class file on line 337 As for the IP addresses mentioned - 46.229.168.163 - 46.229.168.151 - 46.229.168.149 - have a look here: https://whatismyipaddress.com/ip/46.229.168.163 https://whatismyipaddress.com/ip/46.229.168.151 https://whatismyipaddress.com/ip/46.229.168.149 and here https://www.abuseipdb.com/check/46.229.168.163 https://www.abuseipdb.com/check/46.229.168.151 https://www.abuseipdb.com/check/46.229.168.149 Not sure what all that is about, but you may want to consider blocking those IP addresses or possibly the entire range - 46.229.168.0 thru 46.229.168.255. And I didn't check the IP addresses in your first post about the error messages.

1 - I separated out the error_log entries you provided. 2 - What warning are you seeing? For the PHP version - did you change the entire hosting plan to 5.4.45 or just the directory/sub-domain that your phpVMS is in? As a test..... in .../core/lang/en.lang.php on line 31 change 'email.pilot.retired.subject' => SITE_NAME.': You\'ve been marked as retired', to 'email.pilot.retired.subject' => 'SITE_NAME'.': You\'ve been marked as retired', basically adding a ' on either side of SITE_NAME - save the file and retest. If it works - GREAT -- if not, revert back to the original SITE_NAME without the ' on either side. Let us know what happens.

When the conversion from 2.1.x was done, were the database tables updated to add the additional table fields and new tables? To quickly see - In the Schedules table, are columns for week1, week2, week3, week4 ? Is there a Ledger table? There are several other items added to the 5.5.2 database

@Skytraveler For clarification: PIREP hours don't update when you approve the PIREP? PIREP hours do update after running the maintenance script? Is this something new, or has it been doing it for a while? If new, what were the last modules your added or files you edited since it was working correctly? You already stated you are on phpVMS 5.5.2 Was this a conversion from phpVMS 2.1.x or a totally new install at some point? What PHP version? What MySQL/MariaDB version?

Are there any errors listed in the error_log file? Any errors shown in the console in Chrome? Any chance your site relies on ionCube or ionCube loader? What version of MySQL or MariaDB are you using?

Switch back to the crystal skin and see if it works from there. If so, the issue is somewhere in your skin.

Looks like you aren't using the default admin panel skon. Unless someone else is using this exact addon admin panel skin it may be difficult to get an answer to your issue. Can you change the width of the columns using your mouse? Any chance you can revert to the default admin skin?

Do the conversion and apply to the crystal skin. Change your site skin to crystal to check it. If it works on crystal and not on your present skin, contact the skin developer to help you out. What skin are you using?

And there are also several American Airlines, Southwest Airlines - and many others too. If someone wants to open a VA representing a certain airline that already has a VA, there is no harm in it.

What other PHP versions are available from your host?

I am pretty sure that phpVMS 2.1.936 isn't going to work with PHP 7.1.33 Is this your original install of phpVMS 2.1.936 or a new install?

If going to https - I get a site is not secure warning. continuing still gives the 403 error. Tried in two different browsers.

I'm getting a 403 Forbidden error. Anyone else getting that too?

You are responding to a message thread that is over 10 years old. It may be best to start a new message thread and state - in detail - what issues you are experiencing. Include: phpVMS version PHP version MySQL/MariaDB version Skin name

Ok - new install then.... I would recommend you start over from scratch - delete it all.... files, database - all of it. Install fresh. Do NOT add any skins or modules - no SmartCARS to begin with either. Everything default. Then try adding a few airports, aircraft and schedule - finally test EVERYTHING. once it is all working dorrectl, add one skin or addon module at a time and re-test everything again.. including adding and importing aircraft, airports and schedules. It may be a long process, but you should find what is causing your issues. Installing and adding skins/modules without testing is a recipe for disaster. Also, use the console in Chrome (or other browsers) to check for errors. There should also be an error_log file in the directory where phpVMS is installed and in the phpVMS admin directory as well. Check these for possible errors too.

Go here and open a new issue https://github.com/nabeelio/phpvms

Excellent, looking forward to the update!

If it shows 10.2, that is most probably MariaDB. And phpVMS doesn't play nice with MariaDB 10.2 or greater. Is this a new install of phpVMS or for an existing VA? Have you attempted to export the aircraft table to see what it contains? Are there any aircraft listed for use presently?