ProAvia

I believe it will require additions to the site files (smartCARS module) in order to change the polling interval. At least i think thats how it was done in kACARSII. Let us know what they say....

Have a look at this link: https://paragonie.com/blog/2015/06/preventing-xss-vulnerabilities-in-php-everything-you-need-know Or Goggle... preventing cross site scripting in php

Since you usually use smartCARS, I would suggest you contact them to see if that function can be added to smartCARS. kACARSII has this function, but sadly is no longer available. Chances of any of the freeware clients incorporating this is very slim.

What ACARS client are you using?

Try this for the URL rewrite. # BEGIN - force use of SSL/HTTPS RewriteEngine On RewriteCond %{HTTP_HOST} <domain here> [NC] RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.<domain here>/$1 [R,L] # END - force use of SSL Where <domain here> = virtualair.net I have used that on 3 different sites/domains with success.

Yeah, the rewrite code you show forces any http to automatically become https Regardless of subdomains, what is the full path to the phpVMS install? And where does the actual virtualair.net domain name point to in the folder structure? I think most sites with crew center type skins still have the normal installed folder and have /crew within that installed folder (not to be confused with the install folder in the phpVMS folder structure - which you should have deleted after installation). Mine is: /home/<user>/public_html/<VA_name>/phpvms/<phpvms_installation> And any/all skins (CrewCenter inclued) are in: /home/<user>/public_html/<VA_name>/phpvms/<phpvms_installation>/lib/skins/<all_skins_folders_here> Could be your folder structure isn't supposed in any of the ACARS clients Yes, you should go thru all the files and change any calls mentioning http to https - no need to do the URL's in the comments sections though. My bet is something is blocking the ACARS clients from accessing the site do to an http call when it should be https.

Your map appears to be working correctly on my Android tablet. Have you rectified the issue? On another note, someone posted on Avsim that your site was hacked.....https://www.avsim.com/forums/topic/569461-deltavirtualorg-hacked/ ..... might want to check that out just to be safe.

A couple possibilities... It looks like you are using SSL/TLS certificate on your site... so use https instead of http in the base URL Intead of .....//crew.virtual.net - use ....//virtualair.net/<path to phpvms install folder> Do you have error logging enabled and are there any error showing in error_log?

According to the skin readme file, it shouldn't be installed in "vCrewMini-phpvms-skin-master". I suggest you re-read the readme file and place the files in the correct location.... lib/skins/vcrew_mini_v1 So in the skins folder you should have..... crystal vcrew_mini_v1 ... folders

With a default install, all admin functikns are present. Possibly you have a corrupt download. Try downloading a freh copy from Github and do a fresh install. Before adding a new skin or any addons, test out all default functions.

I believe vmshost now offers PHP 7.2 and suggest you use that version. Version 7.0 and 7.1 may be dropped. Do you have a URL to where you got the skin from? Is it freeware or payware? The skin probably shouldn't be installed in "vCrewMini-phpvms-skin-master". Try installing the skin to "vCrewMini" instead or review the install instructions that came with the skin.

What version of phpVMS? What version of PHP? Do the skin files end in tpl or php?

All according to what you want to do. For me, each has its place. Discord is good for text chat, PM and the occasional voice session. Members can log on from computer or mobile device. No costs involved. Teamspeak is voice only and if you run it locally, you or the member running the server have full control. Computer access only unless you pay for the mobile app.

Just another reason to almost NEVER install anything sim related in Program Files (x86) or Program Files.

A warning such as this will not make your site inaccessible. It's just a Warning, not an Error. Did you happen to install an addon admin skin? If so, change back to the default admin skin. Did the site ever load correctly after you install it? I am guessing that phpVMS is installed in /home/singap08/public_html/operations - is that correct? Are you also using the default crystal skin or an addon skin? In /admin/templates/sidebar_schedules.php line 1 is: <?php if(!defined('IN_PHPVMS') && IN_PHPVMS !== true) { die(); } ?> --- I don't think that line is actually needed. Place "//" before the word 'if' (that will comment out the line), saved the file and try again. Although, that line 1 appears in most all of the template files anyway.

We use both. We have had a TeamSpeak server running for several years. It is mostly used during online events or if I member is having computer or sim issues and we need to discuss using voice. Recently, we set up a Discord server - this has allowed quicker "chat" type messages, PM's and the occasional voice session. I still think we will use TeamSpeak for any online events, as we also usually use JoinFS for multiplayer. I believe your are limited to 32 user slots if you run a TS3 server locally - which is how we run ours. Running locally is free - but someone has to run the server so others can connect. We usually have ours running on my old laptop (along with JoinFS) and use a free DNS service so our named IP address doesn't change. No-IP.com is our free DNS provider - and they also offer a free DNS client to parse our IP address and 'marry' it to our named IP address. There are probably other providers as well.

I would start fresh. New install and new database. As I mentioned, additional tables are added to the DB in 5.5.2

I believe iCrewLITE is for phpVMS 5.5.2 and doesn't work in phpVMS 2.1.x Additionally, you will have issues with phpVMS 2.1.x under PHP 5.6 Search for phpVMS 5.5.2 (Simpilot version by DavidJClark) - or use the updated version 2 available here in the forums or on Github. I would recommend 5.5.2 for now. Lots of skins and addon modules will work with it. If you already have a lot of data in your database, you will have to move that over to the new install of 5.5.2 - 5.5.2 adds several new tables to the database along with some additional columns for the existing tables from 2.1.x

As a start.... What version of phpVMS are you using? What version of PHP? Where did you download the iCrewLITE skin from... URL? Chances are the skin is not installed correctly or the skin is not compatible with the phpVMS version you are using.

Great that you have it now working properly. Any chance you will be releasing these skins for others to freely use?

What version of phpVMS? What version of PHP? Where did you download the skin from ... URL?

My very basic understanding is that using different jquery versions can cause all sorts of issues. And converting phpVMS to use a newer jquery version is going to require a lot of code changes. Since you said your skins are custom, any chance you can get them working with the same jquery versions presently used by phpVMS? Maybe reach out to other skin developers (see the forum here on site) and see what they suggest. Once you get these skins working correctly, any chance you will release them as freeware for others to use?

I have not made these changes to "local.config.php" and I get error_log to show errors.

In the root folder of phpVMS should be a file named error_log. Also, at least in my PHP 7.2 with my host, I needed to create a ".user.ini" file which includes a directive to enable logging of errors (this file supposedly overrides the php.ini file on a folder by folder basis). .user.ini - file contents for error logging error_reporting = 32759 display_errors = On display_startup_errors = Off log_errors = On log_errors_max_len = 0 error_log = /<path to phpvms install>/error_log <path to phpvms install> can include "home/public_html/<rest of path>/error_log" I also have the same thing set up in my /admin folder to show admin errors. I suggest changing back to the default user and admin skins and test the log in again. If its working in the default skins, there is probably something messed up in your custom skins.

What skin are you using? If the user closes their browser and reopens it - then goes to the site and uses the correct log in details, are they able to log in correctly? Are there any errors showing in the error_log?