Installation FAQ's
Last updated
Was this helpful?
Last updated
Was this helpful?
To remove the public from the URL create a .htaccess file in the root folder and write following code.
To remove the public from URL and Force HTTPS redirection create a .htaccess file in the root folder and write the following code.
For more detail read article :
NOTE: Remove Public not work for Localhost and sub folders.
Its work with any domain and subdomain only.
In this guide you will know how to remove public from url. To Remove public from url your server must have enabled the mod_rewrite. header to check whether it's enabled or not you can run following and check according to screenshot
To remove the public from the URL in LightSpeed Server -> create a .htaccess file in the root folder and write following code.
To remove the public from URL and Force HTTPS redirection in LightSpeed Server -> create a .htaccess file in the root folder and write the following code.
To Hide or Denied Access .env and create .htaccess file in the root folder and write the following code.
Debug mode will help you to track the error on your website. It is not all preferred to turn the debug mode on live site for a very long time.
How to turn to debug mode on
Login to your FTP account.
Open and edit .env file.
Change
To
Save and upload the file.
false means debug mode is OFF
true means debug mode is ON
A 419 error in Laravel can occur when a user's session has expired and sessions not save. Laravel uses the 419 status code to indicate that the user's session has expired and sessions not save.
To fix this error, you can try the following:
Its not script issue.
Follow mentioned PHP INI settings.
Increase the session lifetime: You can increase the session lifetime in your config/session.php file to prevent the session from expiring too quickly.
Check for session data integrity: Ensure that the session data is not lost or corrupted by checking that the session data is still present in the storage.
Check for Authentication : Ensure that the user is authenticated before allowing access to protected routes or resources.
Make sure PHP version 8.2.4 and use all following PHP settings. It shows due to the session not save in hosting.
If still you are experiencing an 419 error, you should contact your hosting provider or web administrator to troubleshoot the problem and find a solution. They will be able to examine the server logs to determine the cause of the error and take appropriate action. its not script related issue.
If you getting this error SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes (SQL: alter table 'permissions add unique permissions_name_guard_name_unique (name, 'guard_name')). Please Update your server setting.
First Solution: Go to Project-directory\app\Providers\AppServiceProvider.php
To solve this issue you will have to check APP_KEY which is located within your . env (environment) file. don't change or remove it. also check .env file not missing.
Most of times .env file not missing its just hide , so please make sure its not hide.
cPanel show files Quick Steps:
Log into cPanel & click “File Manager” under the files panel.
Click “settings” in the top right of the file manager.
Choose the Document Root (usually you can leave this as the default)
Check the box titled “Show Hidden Files (dotfiles) & click Save.
An internal server error is a general term used to describe a problem that occurs when a server is unable to process a request from a client. This can happen for a variety of reasons, such as a problem with the server's or hardware, a misconfigured server, or an issue with the client's request.
When an internal server error occurs, the server will typically return a message indicating that there was an error and that the request could not be fulfilled. This message is often accompanied by an error code, such as "500 Internal Server Error."
Some Solution :
Please check the .htaccess file configuration.
Check PHP version 8.2.4
Check port 80
Check all files extracted properly specially vendor folder.
Exceeding server resources
Corrupted server files
If still you are experiencing an internal server error, you should contact your hosting provider or web administrator to troubleshoot the problem and find a solution. They will be able to examine the server logs to determine the cause of the error and take appropriate action. its not script related issue.
Please check database privilege. it must be ALL PRIVILEGES. if you don't know how to give it please contact to hosting provider.
You are getting this error because you don't enable a zip archive extension on your server. enable zip archive extension and issue will resolved. if you don't know how to enable it please contact to hosting provider. its not script related error.
You are getting this error because you don't enable a curl extension on your server. enable curl e extension and issue will resolved. if you don't know how to enable it please contact to hosting provider. its not script related error.
To Enable cURL Using EasyApache on WHM:
Log in to WHM as the 'root' user.
Either search for "EasyApache" or go to Software > EasyApache
Scroll down and select a build option (Previously Saved Config)
Click Start "Start customizing based on profile"
Select the version of Apache and click "Next Step".
Select the version of PHP and click "Next Step".
Chose additional options within the "Short Options List"
Click Exhaustive Options List.
Find and select the option for cURL.
Click curl, and then click Save and build.
A 404 error is an HTTP status code that indicates that a requested web page or resource cannot be found on a server. 404 means file not fount, its not script issue.
This can happen for a number of reasons, including:
Check port 80
Check all files extracted properly.
Incorrect URL
The server is down
If still you are experiencing an 404, you should contact your hosting provider or web administrator to troubleshoot the problem and find a solution. They will be able to examine the server logs to determine the cause of the error and take appropriate action. its not script related issue.
A 403 error is an HTTP status code that indicates that the client (i.e. the user's browser) is not authorized to access the requested resource. This error message is often displayed when a user attempts to access a website or webpage that they do not have permission to view. Your user who did not get permission. So you edit the user role and then update
Certain users to access certain pages or sections. In this case, a 403 error message may be displayed if the user is not authorized to view the requested resource.
A payload error in Laravel is typically caused by an issue with the data being passed to the server during an API request. This can be caused by a number of factors, including missing or incorrect data, invalid data types, or incorrect formatting of the data.
Please check File and folder permissions for Shared Hosting
File and folder permissions for VPS
The error message you provided, "could not find driver (SQL: select * from settings limit 1)", suggests that there is an issue with the database driver configuration in your server or cpanel.
Check Database Configuration:
Open the .env file in your Laravel project and ensure that the DB_CONNECTION parameter is set to the correct database driver (e.g., mysql).
Verify Database Extension:
Ensure that the necessary PHP extensions for your chosen database are installed and enabled on your server. For example, if you're using MySQL, make sure the pdo_mysql extension is enabled.
Check Database Connection:
Ensure that your database server is running and that the connection details in your .env file (such as DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, and DB_PASSWORD) are correct.
Restart Server:
After making any changes, it's a good idea to restart your server to apply the updates.
Verify PHP Version:
Make sure you're using a compatible PHP version for your Laravel version.
Database Permissions:
Check necessary permissions to access the database.
its possible solution : Check for Caching Issues If you're working in a shared hosting environment, you might also need to check whether there is a server-side caching mechanism (like Varnish or Cloudflare) that could be causing .env changes to not reflect.
php artisan config:clear php artisan cache:clear php artisan config:cache
restart server
Check folder permissions as mentioned :
Check folder permissions as mentioned :
