My server has Plesk and I have mydomain.com with frontend in Vue and backend in api.mydomain.com with laravel. Before, when I went to mydomain.com/clients and tried to refresh the page, I got an error with Phusion Passenger. I have disabled Phusion Passenger on this domain but I don't remember how I did it.
Now, I have the same problem with the same front and back system. The only difference is that both domains are subdomains, that is, I have front.domain.es and api.domain.es.
If I refresh front.domain.com it works perfectly. If I navigate from the system menu it works fine. But, if I am in front.domain.com/clients for example and I try to refresh page, I get Pushion Passenger error.
Important comment that the system work perfectly, just when you try to refresh the page has this error. On the first example that I comment, now works perfecty without Passenger, I can refresh without problem, but I don't remember how I did it.
I want to disable Phusion Passenger for this hosting on plesk or domain or whatever, I hope you can help me!
Thank you very much!!
Log File:
[ E 2023-02-02 08:44:42.0486 476333/Tf age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/vhosts/domain.com/front.domain.com: The application process exited prematurely.
Error ID: dbcc318c
Error details saved to: /tmp/passenger-error-BX09me.html
Go in Tools&Settings >> PHP Setting
In top of the page you should find this " Select the PHP handlers you want to make available. You can install additional handlers using the Plesk Installer. "
Follow the link and will take you to Plesk Installer, there you can enable/disable modules including fusion
Related
I've created my first full Laravel tool. (Yiehaaa).
I'm looking to host it somewhere for my customer as he wants to be able to use it from different PC's in his network.
Therefore I was thinking to put it on a Synology NAS (DS215j) which is already available.
I took following steps :
Install WebStation
Install PHP7
Install Nginx with MariaDB10
Imported all tables
My Webstation is up-and-running, telling Nginx is running with PHP7.
Under PHP settings, I enabled : mysqli, openssl and pdo_mysql.
In the end, I created a Virtual host PORT based (on port 85 for http and port 86 for https) and connected the main folder to "web/maintoolfolder/public".
As http back-end server Nginx is chosen, with PHP 7.0
When I now open following url http://nasname:85 , I get to see my index.php page without any problem ! So yeahhhhh...
But, whatever link I click which needs to open one of my routes, I always get the error message "404 page can not be found".
Strange thing is that this 404 page is not even the own created Laravel 404 page.
What am I doing wrong ? Why can't I move between the different pages?
Thanks in advance for any help.
best regards,
Davy
I have a problem when it comes to registration as in confirmation was not sent to my email. Aside from this, it keeps returning to the registration page, no progress at all. What shall I do?
Anyway I'm using Joomla 3.6.2 with VM 3.0.18 installed
To start at somewhere:
1. Make sure that mailer is configured under Global Configuration \ server \ Mail Settings.
2. See if mails are sent locally. Webservers like Open server or Denwer have an option to get your emails locally, dumped to some folder as files.
3. Also see if options for Virtuemart registering are okay.
I've got a Laravel app setup locally with (what seems to me) very poor performance as you can see below:
My setup:
W8 on a pretty fast laptop with SSD
XAMPP 3.2.1
Laravel 4.1.*
Clockwork 1.* (only added the controller event as desribed in the docs)
Debug mode true
The scenario described:
A logged in user access a page with a list of prospects : 1216ms
Then the user logs out : 1164ms
Finally the user is redirected to the login page : 1165ms
As you can see in every single request the bottleneck is the "Router Dispatch" event. What can I do to dig further, and most importantly what can I do to improve its duration?
Or maybe because this is a dev environnment these are expected numbers? (I don't believe so, but I might be wrong).
After updating my XAMPP to the latest and Laravel to 4.2, this just got fixed by itself.
I cannot login to Drupal after attempting php 5.4 update.
I have two users, the default admin from install and a user level account with limited permissions. After logging in at mysite.com/user/login I am redirected to mysite.com/user/1 with the following message displayed "You are not authorized to access this page." I get the same when I attempt mysite.com/admin
I have commented out the $base_url and $cookies_domain entries in settings.php with no luck.
If I attempt to login with bad credentials my login is denied. So credentials verification is working.
Also, I purged the SESSIONS table in the database. I have attempted login many times after the SESSIONS purge but there are no new rows being created in that table.
Somehow I am passing the credentials verification stage but then the session fails to save to the database... ergo my "not authorized" message.
I'm not the least bit familiar with what is going on in Drupal core. Normally my Drupal installs just work.
Do you think this is a Drupal issue or PHP? Have I missed some stupid setting in php.ini?
p.s. - I actually have two apache virtual hosts, one with a Drupal 6 install and another with my Drupal 7... this login issue is happening to both installs. (Probably because they share PHP ?)
I greatly appreciate any thoughts or suggestions :-)
Seems that you try several attempts there. Anyway I would suggest you the following:
Clear cache and run cron: $ drush cc all && $ drush cron
Start the: /user/logout # to stop login sessions and try to login again.
Add to your index.php:
error_reporting(E_ALL | E_ERROR | E_WARNING | E_PARSE | E_NOTICE);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
Also check the watchdog table if you can recognize anything there.
I'm on PHP 5.4.3 and not having any issues with that. If you will not find any workaround for that, PHP 5.3.10 is the minimal version required for D8 so a downgrade to it will be OK.
Did you try to make a fresh install of Drupal on your new PHP version?
Essentially, when you don't visit my Jekyll application on Heroku for an hour, you see this error message the first time the app fires back up:
Forbidden
no access permission to `/'
WEBrick/1.3.1 (Ruby/1.9.2/2011-07-09) at franklovecchio.herokuapp.com:80
Then, after a page reload, all is magically fine. I don't recall seeing this with my other Jekyll Heroku apps. The source is here: https://github.com/franklovecchio/frank.lovecch.io . Anybody see this and know what the problem is?
Do you only have one web worker? Heroku sites with only one process automatically go idle after an hour of inactivity. Then, when a visitor hits your site, the Jekyll server has to spin up again, but it hasn't actually generated the root index.html file yet, so you get a "forbidden error" (this is what Jekyll's built-in server returns when it hasn't completely generated the site yet).