Common questions

This page highlights some common questions or issues and mentions guidelines to get around it.

Login not working

This mostly happens on running debug builds and you may have missed adding SHA-1/256 hashes from your debug keystore to your Firebase project & Facebook app.

Once your app is uploaded and approved by Play Store, you also need to add SHA-1/256 hashes from Play Console to your Firebase project & Facebook app. You need to go to your Play Console account > (app) > Setup > App Integrity. You need to copy and add SHA-1/256 values from here, add them to your Firebase project. Then you need to create Base64 version from the SHA-1 hash in Play Console using https://bit.ly/vpz-keyhash and add it your Facebook app.

Unlicensed

If your server has just started showing Unlicensed recently, it occurs when you try to use your purchase code on an IP address than was originally activated with. This mostly happens in case of shared hosting or during server migrations.

If you are having trouble with activating the script on your new server, you can contact us for instructions on how to unlock it.

Server security

However, the Muly script is secure enough to prevent your from common vulnerabilities like SQLi, XSS etc. But for advanced users, you can add even more security layer to your API easily.

To prevent anyone from directly accessing your API endpoints from browser and scraping information, you can set the server_api_key in config.xml file and API_KEY in .env file to a random alpha-numeric string e.g., S7YF99JFYLNMB3DLCNWF2R726BQ4HKTZ. You can use https://bit.ly/etoolkit-password-generator to create those for you.

You can also enable SSL pinning to protect your app from MITM (man-in-the-middle) attacks. But you must be aware than in case the certificate which you have pinned (intermediate or leaf) changes (in case of renewals) your existing users using old app will not be able to connect to the server so you must apply updates in time.

To enable SSL pinning, first generate SHA-256 hash from your website's chain of trust using http://bit.ly/generate-ssl-sha256. Then set the ssl_pinning_enabled to true in config.xml file. Put the generated hash of either leaf/intermediate certificate in ssl_pinning_certificate prefixed with sha256/. You will also need to update ssl_pinning_domain to your server hostname.

Missing 'settings' table

If you encounter a similar error when running php artisan migrate command during update, try running below commands in project directory:

rm bootstrap/cache/config.php
rm storage/.installed

php artisan migrate

touch storage/.installed
php artisan config:cache

FFmpeg on cPanel

The installation instructions for LAMP/LEMP already cover FFmpeg installation on cloud servers. But if you are using cPanel, there's no FFmpeg installed by default. In order to install it, you must have root access to server.

If you have root access and wish to install FFmpeg on cPanel, please SSH into the server as root and run below commands:

git clone https://github.com/q3aql/ffmpeg-install
cd ffmpeg-install
sudo make install

ffmpeg-install --install release

Resetting password

In rare cases, one may be locked out of their administrator account following a change they may be trying to make in their user account.

In such event, you can request a password reset email using the Forgot Password option on login page but it assumes you had setup an email service during installation. If you haven't, you can't regain access to your account from command-line.

To reset administrator password from command-line, login to server over SSH and navigate to Muly installation folder and run below command:

php artisan tinker

In the tinker shell, run below statements in order:

$user = App\User::query()->where('role', 'admin')->firstOrFail();
$user->password = Hash::make('12345678');
$user->save();

You should now be able to login using 12345678 as password.