• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Weird Apache(?) Problem

C

Captaffy

Guest
I am not sure this is an Apache issue to be honest, but it correlates to when I updated httpd to 2.0.52-32.3.

Whenever a user visits any site hosted on the server for the first time, the page doesn't load. It's as if the server doesn't exist. If they refresh the page, it works fine and will continue to work until their IP address changes? Does anyone have any idea what the problem could be?

There are also a lot of '..reading..' states that show up in Apache Server Status that eventually time out. I believe these are the users that are not seeing the pages, but at least it suggests Apache is actually talking to them. (Originally I thought it was a bind problem.)
 
By the way, the error I get in Firefox is -

Unable to connect
Firefox can't establish a connection to the server at ...
 
Back
Top