• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Plesk www is not accesible at all, please help!

BigMaras

New Pleskian
Serwer is up and running, hoested website is up and running but plesk www is not accesible at all :(

below log:
[2019-03-11 02:19:04.931] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-12 02:19:04.237] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-13 02:19:05.338] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-14 02:19:05.360] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-15 02:19:04.511] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-16 02:19:05.398] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-17 02:19:04.806] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-18 02:19:04.778] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-19 02:19:05.183] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-20 02:19:04.607] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-21 02:19:05.233] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-22 02:19:04.745] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-23 02:19:04.642] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-24 02:19:05.398] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-24 06:30:01.672] ERR [panel] Error: Invalid response from roller 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

[2019-03-25 02:19:04.296] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-25 06:31:16.237] ERR [panel] Error: Invalid response from roller 504 Gateway Time-out: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

[2019-03-26 02:19:04.097] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-26 06:30:58.432] ERR [panel] Error: Invalid response from roller 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

[2019-03-27 02:19:04.578] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-27 06:30:46.032] ERR [panel] Error: Invalid response from roller 504 Gateway Time-out: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

[2019-03-28 02:19:04.501] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-28 06:34:09.817] ERR [panel] Error: Invalid response from roller 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

[2019-03-29 02:19:04.051] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-29 06:31:07.494] ERR [panel] Error: Invalid response from roller 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

[2019-03-30 02:19:04.739] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-30 06:33:13.675] ERR [panel] Task failed: id=138, pid=17930, type=aps-cache, error=
[2019-03-30 06:34:00.917] ERR [panel] APS Catalog error:
[2019-03-30 06:34:00.921] ERR [panel] APS Catalog error:
[2019-03-30 06:34:00.921] ERR [panel] APS Catalog error:
[2019-03-30 06:34:00.922] ERR [panel] APS Catalog error:
[2019-03-31 03:00:04.398] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-03-31 06:32:51.944] ERR [panel] Error: Invalid response from roller 502 Bad Gateway: <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

[2019-04-01 02:19:04.635] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
[2019-04-01 06:30:06.590] ERR [panel] Error: Invalid response from roller 504 Gateway Time-out: <html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>

[2019-04-02 02:19:05.935] ERR [extension/pagespeed-insights] Domain does not answer with HTTP status code 200. Please check manually!
 
Besides the Pagespeed part: You can open the domain WITH www in a browser and it is logged with code 200 in access_log?
 
Back
Top