<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Website broken following migration to greenby in Everything else</title>
    <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2036648#M40721</link>
    <description>&lt;P&gt;Thank you &lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/26334"&gt;@plusnettony&lt;/a&gt; &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@104CD63F9302A50EF5EC70FE32BB8AA1/images/emoticons/smiley.gif" alt="Smiley" title="Smiley" /&gt; Current status of the specific problems discussed in the thread:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="greenby 403 error.gif" style="width: 999px;"&gt;&lt;img src="https://community.plus.net/t5/image/serverpage/image-id/62207iF9C851F4E59DDFD2/image-size/large?v=v2&amp;amp;px=999" role="button" title="greenby 403 error.gif" alt="greenby 403 error.gif" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="greenby 500 error.gif" style="width: 999px;"&gt;&lt;img src="https://community.plus.net/t5/image/serverpage/image-id/62206i85CA5BDEE1150A45/image-size/large?v=v2&amp;amp;px=999" role="button" title="greenby 500 error.gif" alt="greenby 500 error.gif" /&gt;&lt;/span&gt;&amp;nbsp; &lt;/P&gt;
&lt;P&gt;A full and detailed technical explanation for these two significant problems is now required as a matter of urgency. There are numerous other short-lived issues (typ &amp;lt; 10 minutes) recorded on all F9/PN A/Cs (PN hosted as well as Greenby hosted) at various times which I'm just ignoring for now in order to focus on the more significant problems which were experienced and not exactly resolved in a timely manner. &lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;It needs to be ascertained whether these issues were down to:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;PN or Greenby (if not both !)&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; The specific server allocated to the A/C&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; A change in server IP&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Server configuration in general&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Apache configuration in particular&lt;/LI&gt;
&lt;LI&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Incompetence or data mis-management during A/C migration(s)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;In addition, I note that Ye Olde Apache Version 2.4.58 which was apparently released 19/10/2023 is still being used. Why is this when there are quite so many publicly announced problems, vulnerabilities and security issues with non-current versions, all of which were fixed in Version 2.4.66 which was apparently released 04/12/2025.&lt;BR /&gt;&lt;BR /&gt;I just cannot in any way understand why on earth a 'new' company is apparently setting up 'new' customers on some allegedly 'new' system but is currently using such relatively ancient software &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@7617B13E24C0CCAE119AD01B2BB73839/images/emoticons/rolleyes.gif" alt="Roll_eyes" title="Roll_eyes" /&gt; &lt;BR /&gt;&lt;BR /&gt;Is this going to end up as a movie about some 12-year-olds who've found a bunch of servers in a skip behind an IT recycling warehouse and are setting this up in their parents' garage perhaps &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@8BBE3DF35B52AAD1B52BEBDC4974E1AD/images/emoticons/tongue.gif" alt="Tongue" title="Tongue" /&gt; Because whilst that kinda thing may well have worked out quite well for the likes of Gates, Bezos and Zuckerburg et al, it's far from guaranteed to work in general as countless thousands of others would no doubt be able to confirm from much personal experience with trying !&lt;BR /&gt;&lt;BR /&gt;Given my very positive experiences with a different ENIX brand, I'm seriously disappointed with what Greenby are providing, how they are doing it and with all the apparent issues that PN customers have been having with their migration in general &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt; So much so that it will inevitably be influencing my decisions on future hosting contracts. I very much regret suggesting to other customers that things will be so much better once email and webspace is finally migrated away from PN. Rather foolishly with hindsight, I just assumed that we'd all end up with a service much the same as that I was currently experiencing eventually, albeit one with restricted functionality or performance. I was most certainly not expecting the dog's dinner that we seem to have been served no matter who or what is responsible for it's creation.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;However, the all-important Question Of The Day is: Just how many well known problems does there need to be before antique software applications are actually updated to more current and hopefully somewhat less bug-ridden versions ? Answers ... on a postcard of course ... because my email is, shall we say, more than a little cranky and unreliable at times plus my website may or may not be working should you try to contact me that way instead &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@8BBE3DF35B52AAD1B52BEBDC4974E1AD/images/emoticons/tongue.gif" alt="Tongue" title="Tongue" /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[QUOTE]&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.66&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-66200: Apache HTTP Server: mod_userdir+suexec&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; bypass via AllowOverride FileInfo (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_userdir+suexec bypass via AllowOverride FileInfo&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vulnerability in Apache HTTP Server. Users with access to use&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the RequestHeader directive in htaccess can cause some CGI&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; scripts to run under an unexpected userid.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server: from 2.4.7 through&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.4.65.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.66, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Mattias Ã…sander (UmeÃ¥ University)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-65082: Apache HTTP Server: CGI environment&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; variable override (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Improper Neutralization of Escape, Meta, or Control Sequences&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vulnerability in Apache HTTP Server through environment&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; variables set via the Apache configuration unexpectedly&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; superseding variables calculated by the server for CGI programs.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server from 2.4.0 through 2.4.65.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.66 which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Mattias Ã…sander (UmeÃ¥ University)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-59775: Apache HTTP Server: NTLM Leakage on&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Windows through UNC SSRF (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Server-Side Request Forgery (SSRF) vulnerability&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Â in Apache HTTP Server on Windows&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; with AllowEncodedSlashes OnÂ and MergeSlashes OffÂ&amp;nbsp; allows to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; potentially leak NTLM&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; hashes to a malicious server via SSRF and malicious requests or&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; content&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.66, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-58098: Apache HTTP Server: Server Side&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Includes adds query string to #exec cmd=... (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Apache HTTP Server 2.4.65 and earlier with Server Side Includes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (SSI) enabled and mod_cgid (but not mod_cgi) passes the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; shell-escaped query string to #exec cmd="..." directives.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server before 2.4.66.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.66, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Anthony Parfenov (United Rentals, Inc.)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-55753: Apache HTTP Server: mod_md (ACME),&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unintended retry intervals (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; An integer overflow in the case of failed ACME certificate&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; renewal leads, after a number of failures (~30 days in default&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configurations), to the backoff timer becoming 0. Attempts to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; renew the certificate then are repeated without delays until it&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; succeeds.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server: from 2.4.30 before 2.4.66.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.66, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Aisle Research&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: Fix handling of 304 responses from mod_cache. PR 69580.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Stefan Eissing]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2/mod_proxy_http2: fix a bug in calculating the log2 value of&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; integers, used in push diaries and proxy window size calculations.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR69741 [Benjamin P. Kallus]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.6.5&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - New directive `MDInitialDelay`, controlling how longer to wait after&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a server restart before checking certificates for renewal.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Michael Kaufmann]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Hardening: when build with OpenSSL older than 1.0.2 or old libressl&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; versions, the parsing of ASN.1 time strings did not do a length check.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Hardening: when reading back OCSP responses stored in the local JSON&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; store, missing 'valid' key led to uninitialized values, resulting in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; wrong refresh behaviour.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.6.6&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fix a small memory leak when using OpenSSL's BIGNUMs. [Theo Buehler]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fix reuse of curl easy handles by resetting them. [Michael Kaufmann]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: update to version 2.0.35&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; New directive `H2MaxStreamErrors` to control how much bad behaviour&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by clients is tolerated before the connection is closed.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Stefan Eissing]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; * mod_proxy_http2: add support for ProxyErrorOverride directive. PR69771&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mpm_common: Add new ListenTCPDeferAccept directive that allows to specify&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the value set for the TCP_DEFER_ACCEPT socket option on listen sockets.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Ruediger Pluem]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Add SSLVHostSNIPolicy directive to control the virtual&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; host compatibility policy.&amp;nbsp; PR 69743.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.6.2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fix error retry delay calculation to not already doubling the wait&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; on the first error.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.6.1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Increasing default `MDRetryDelay` to 30 seconds to generate less bursty&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; traffic on errored renewals for the ACME CA. This leads to error retries&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; of 30s, 1 minute, 2, 4, etc. up to daily attempts.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Checking that configuring `MDRetryDelay` will result in a positive&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; duration. A delay of 0 is not accepted.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fix a bug in checking Content-Type of responses from the ACME server.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Added ACME ARI support (rfc9773) to the module. Enabled by default. New&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; directive "MDRenewViaARI on|off" for controlling this.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Removing tailscale support. It has not been working for a long time&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; as the company decided to change their APIs. Away with the dead code,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; documentation and tests.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed a compilation issue with pre-industrial versions of libcurl.&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.65&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-54090: Apache HTTP Server: 'RewriteCond expr'&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; always evaluates to true in 2.4.64 (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A bug in Apache HTTP Server 2.4.64 results in all "RewriteCond&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; expr ..." tests evaluating as "true".&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.65, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.64&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-53020: Apache HTTP Server: HTTP/2 DoS by&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Memory Increase (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Late Release of Memory after Effective Lifetime vulnerability in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Apache HTTP Server.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server: from 2.4.17 up to 2.4.63.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.64, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Gal Bar Nahum&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-49812: Apache HTTP Server: mod_ssl TLS&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; upgrade attack (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In some mod_ssl configurations on Apache HTTP Server versions&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; through to 2.4.63, an HTTP desynchronisation attack allows a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; man-in-the-middle attacker to hijack an HTTP session via a TLS&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; upgrade.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Only configurations using "SSLEngine optional" to enable TLS&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; upgrades are affected. Users are recommended to upgrade to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; version 2.4.64, which removes support for TLS upgrade.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Robert Merget (Technology Innovation Institute)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-49630: Apache HTTP Server: mod_proxy_http2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; denial of service (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In certain proxy configurations, a denial of service attack&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; againstÂ Apache HTTP Server versions 2.4.26 through to 2.4.63&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; can be triggered by untrusted clients causing an assertion in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_proxy_http2.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Configurations affected are a reverse proxy is configured for an&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP/2 backend, with ProxyPreserveHost set to "on".&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Anthony CORSIEZ&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2025-23048: Apache HTTP Server: mod_ssl access&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; control bypass with session resumption (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In some mod_ssl configurations on Apache HTTP Server 2.4.35&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; through to 2.4.62, an access control bypass by trusted clients&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; is possible using TLS 1.3 session resumption.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Configurations are affected when mod_ssl is configured for&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; multiple virtual hosts, with each restricted to a different set&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; of trusted client certificates (for example with a different&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSLCACertificateFile/Path setting). In such a case, a client&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; trusted to access one virtual host may be able to access another&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; virtual host, if SSLStrictSNIVHostCheck is not enabled in either&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; virtual host.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Sven Hebrok, Felix Cramer, Tim Storm, Maximilian Radoy,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; and Juraj Somorovsky at Paderborn University&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-47252: Apache HTTP Server: mod_ssl error log&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; variable escaping (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Insufficient escaping of user-supplied data in mod_ssl in Apache&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP Server 2.4.63 and earlier allows an untrusted SSL/TLS&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; client to insert escape characters into log files in some&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configurations.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; In a logging configuration where CustomLog is used with&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "%{varname}x" or "%{varname}c" to log variables provided by&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_ssl such as SSL_TLS_SNI, no escaping is performed by either&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_log_config or mod_ssl and unsanitized data provided by the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; client may appear in log files.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: John Runyon&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-43394: Apache HTTP Server: SSRF on Windows&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; due to UNC paths (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Server-Side Request Forgery (SSRF) in Apache HTTP Server on&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Windows allows to potentially leak NTLM hashes to a malicious&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; server via&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_rewrite or apache expressions that pass unvalidated request&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; input.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server: from 2.4.0 through 2.4.63.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Note:&amp;nbsp; The Apache HTTP Server Project will be setting a higher&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; bar for accepting vulnerability reports regarding SSRF via UNC&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; paths.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The server offers limited protection against administrators&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; directing the server to open UNC paths.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Windows servers should limit the hosts they will connect over&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; via SMB based on the nature of NTLM authentication.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Kainan Zhang (@4xpl0r3r) from Fortinet&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-43204: Apache HTTP Server: SSRF with&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_headers setting Content-Type header (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSRF in Apache HTTP Server with mod_proxy loaded allows an&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; attacker to send outbound proxy requests to a URL controlled by&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the attacker.&amp;nbsp; Requires an unlikely configuration where&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_headers is configured to modify the Content-Type request or&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; response header with a value provided in the HTTP request.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.64 which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; this issue.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-42516: Apache HTTP Server: HTTP response&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; splitting (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP response splitting in the core of Apache HTTP Server allows&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; an attacker who can manipulate the Content-Type response headers&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; of applications hosted or proxied by the server can split the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP response.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This vulnerability was described as CVE-2023-38709 but the patch&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; included in Apache HTTP Server 2.4.59 did not address the issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.64, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; this issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: xiaojunjie@å®‰æ&amp;#129;’ä¿¡æ&amp;#129;¯æ&amp;#157;­å·žå¸‚æ»¨æ±ŸåŒºæŠ€èƒ½å¤§å¸ˆå·¥ä½œå®¤&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy_ajp: Use iobuffersize set on worker level for the IO buffer&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; size. PR 69402 [Jari Ahonen &amp;lt;jah@progress.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Drop $SSLKEYLOGFILE handling internally for OpenSSL 3.5&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; builds which enable it in libssl natively.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_asis: Fix the log level of the message AH01236.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Github #527 [Michael Kaufmann &amp;lt;mail michael-kaufmann.ch&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_session_dbd: ensure format used with SessionDBDCookieName and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SessionDBDCookieName2 are correct.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Github #503 [Thomas Meyer &amp;lt;thomas m3y3r.de&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_headers: 'RequestHeader set|edit|edit_r Content-Type X' could&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inadvertently modify the Content-Type _response_ header. Applies to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Content-Type only and likely to only affect static file responses.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Eric Covener]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Remove warning over potential uninitialised value&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for ssl protocol prior to protocol selection.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Graham Leggett]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Reuse ProxyRemote connections when possible, like prior&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to 2.4.59.&amp;nbsp; [Jean-Frederic Clere, Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_systemd: Add systemd socket activation support.&amp;nbsp; [Paul Querna,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Jan Kaluza, Lubos Uhliarik &amp;lt;luhliari redhat.com&amp;gt;, Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_systemd: Log the SELinux context at startup if available and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; enabled.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: update to version 2.0.32&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The code setting the connection window size was set wrong,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; preventing `H2WindowSize` to work.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Fixed &amp;lt;&lt;A href="https://github.com/icing/mod_h2/issues/300" target="_blank"&gt;https://github.com/icing/mod_h2/issues/300&lt;/A&gt;&amp;gt;.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Stefan Eissing, Michael Kaufmann]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: update to version 2.0.30&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed bug in handling over long response headers. When the 64 KB limit&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; of nghttp2 was exceeded, the request was not reset and the client was&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; left hanging, waiting for it. Now the stream is reset.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Added new directive `H2MaxHeaderBlockLen` to set the limit on response&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; header sizes.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed handling of Timeout vs. KeepAliveTimeout when first request on a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; connection was reset.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_lua: Fix memory handling in LuaOutputFilter. PR 69590.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Guillermo Grandes &amp;lt;guillermo.grandes gmail.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; * mod_proxy_http2: revert r1912193 for detecting broken backend connections&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; as this interferes with backend selection who a node is unresponsive.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR69624.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy_balancer: Fix a regression that caused stickysession keys no&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; longer be recognized if they are provided as query parameter in the URL.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 69443 [Ruediger Pluem]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.5.2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed TLS-ALPN-01 challenges when multiple `MDPrivateKeys` are specified&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; with EC keys before RSA ones. Fixes #377. [Stefan Eissing]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed missing newlines in the status page output. [Andreas Groth]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_dav: Add API to expose DavBasePath setting.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.5.1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Added support for ACME profiles with new directives MDProfile and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MDProfileMandatory.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - When installing a custom CA file via `MDCACertificateFile`, also set the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; libcurl option CURLSSLOPT_NO_REVOKE that suppresses complains by Schannel&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (when curl is linked with it) about missing CRL/OCSP in certificates.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed handling of corrupted httpd.json and added test 300_30 for it.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; File is removed on error and written again. Fixes #369.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Added explanation in log for how to proceed when md_store.json could not be&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; parsed and prevented the server start.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - restored fixed to #336 and #337 which got lost in a sync with Apache svn&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Add Issue Name/Uris to certificate information in md-status handler&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - MDomains with static certificate files have MDRenewMode "manual", unless&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "always" is configured.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) core: Report invalid Options= argument when parsing AllowOverride&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; directives.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Github #310 [Zhou Qingyang &amp;lt;zhou1615 umn.edu&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) scoreboard/mod_http2: record durations of HTTP/2 requests.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 69579 [Pierre Brochard &amp;lt;pierre.brochard.1982@m4x.org&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.63&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_dav: Update redirect-carefully example BrowserMatch config&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to match more recent client versions.&amp;nbsp; PR 66148, 67039.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Michal Maloszewski &amp;lt;michal.maloszewski canonical.com&amp;gt;,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Romain TartiÃ¨re &amp;lt;romain blogreen.org&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_cache_socache: Fix possible crash on error path. PR 69358.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Ruediger Pluem]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Fail cleanly at startup if OpenSSL initialization fails.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [StephenWall]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.4.31&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Improved error reporting when waiting for ACME server to verify domains&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; or finalizing the order fails, e.g. times out.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Increasing the timeouts to wait for ACME server to verify domain names&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; and issue the certificate from 30 seconds to 5 minutes.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Change a log level from error to debug when Stapling is enabled but a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; certificate carries no OCSP responder URL.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy_balancer: Fix the handling of the stickysession configuration&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; parameter by the balancer manager. PR 69510&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Yutaka Tokunou &amp;lt;tokunou.yutaka@fujitsu.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) Add the ldap-search option to mod_authnz_ldap, allowing authorization&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to be based on arbitrary expressions that do not include the username.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Make sure that when ldap searches are too long, we explicitly log the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error. [Graham Leggett]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Honor parameters of ProxyPassMatch workers with substitution&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; in the host name or port. PR 69233. [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_log_config: Fix merging for the "LogFormat" directive.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 65222. [Michael Kaufmann &amp;lt;mail michael-kaufmann.ch&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_lua: Make r.ap_auth_type writable.&amp;nbsp; PR 62497.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Michael Osipov &amp;lt;michaelo apache.org&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.4.29&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed HTTP-01 challenges to not carry a final newline, as some ACME&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; server fail to ignore it. [Michael Kaufmann (@mkauf)]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed missing label+newline in server-status plain text output when&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MDStapling is enabled.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Restore support for loading PKCS#11 keys via ENGINE&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; without "SSLCryptoDevice" configured.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_authnz_ldap: Fix possible memory corruption if the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AuthLDAPSubGroupAttribute directive is configured.&amp;nbsp; [Joe Orton] &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy_fcgi: Don't re-encode SCRIPT_FILENAME when set via SetHandler.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 69203. [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_rewrite, mod_proxy: mod_proxy to canonicalize rewritten [P] URLs,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; including "unix:" ones.&amp;nbsp; PR 69235, PR 69260.&amp;nbsp; [Yann Ylavic, Ruediger Pluem]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_rewrite: Error out in case a RewriteRule in directory context uses the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; proxy, but mod_proxy is not loaded. PR 56264.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Christophe Jaillet, Michael Streeter &amp;lt;mstreeter1@gmail.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) http: Remove support for Request-Range header sent by Navigator 2-3 and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MSIE 3. [Stefan Fritsch]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_rewrite: Don't require [UNC] flag to preserve a leading //&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; added by applying the perdir prefix to the substitution.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Ruediger Pluem, Eric Covener]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) Windows: Restore the ability to "Include" configuration files on UNC&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; paths. PR 69313 [Eric Covener]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Avoid AH01059 parsing error for SetHandler "unix:" URLs&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; in &amp;lt;Location&amp;gt; (incomplete fix in 2.4.62). PR 69160. [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md: update to version 2.4.28&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - When the server starts, it looks for new, staged certificates to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; activate. If the staged set of files in 'md/staging/&amp;lt;domain&amp;gt;' is messed&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; up, this could prevent further renewals to happen. Now, when the staging&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; set is present, but could not be activated due to an error, purge the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; whole directory. [icing]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fix certificate retrieval on ACME renewal to not require a 'Location:'&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; header returned by the ACME CA. This was the way it was done in ACME&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; before it became an IETF standard. Let's Encrypt still supports this,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; but other CAs do not. [icing]&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Restore compatibility with OpenSSL &amp;lt; 1.1. [ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_tls: removed the experimental module. It now is availble standalone&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; from &lt;A href="https://github.com/icing/mod_tls" target="_blank"&gt;https://github.com/icing/mod_tls&lt;/A&gt;. The rustls provided API is not&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; stable and does not align with the httpd release cycle.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Stefan Eissing]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_rewrite: Better question mark tracking to avoid UnsafeAllow3F.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 69197. [Yann Ylavic, Eric Covener]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: Return connection monitoring to the event MPM when blocking&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; on client updates. [Stefan Eissing, Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.62&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-40898: Apache HTTP Server: SSRF with&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_rewrite in server/vhost context on Windows (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSRF in Apache HTTP Server on Windows with mod_rewrite in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; server/vhost context, allows to potentially leak NTML hashes to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a malicious server via SSRF and malicious requests.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.62 which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; this issue.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Smi1e (DBAPPSecurity Ltd.)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-40725: Apache HTTP Server: source code&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; disclosure with handlers configured via AddType (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A partial fix for CVE-2024-39884 in the core of Apache HTTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Server 2.4.61 ignores some use of the legacy content-type based&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configuration of handlers. "AddType" and similar configuration,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; under some circumstances where files are requested indirectly,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; result in source code disclosure of local content. For example,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PHP scripts may be served instead of interpreted.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.62, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; this issue.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Fix canonicalisation and FCGI env (PATH_INFO, SCRIPT_NAME) for&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "balancer:" URLs set via SetHandler, also allowing for "unix:" sockets&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; with BalancerMember(s).&amp;nbsp; PR 69168.&amp;nbsp; [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Avoid AH01059 parsing error for SetHandler "unix:" URLs.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PR 69160 [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Fix crashes in PKCS#11 ENGINE support with OpenSSL 3.2.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Add support for loading certs/keys from pkcs11: URIs&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; via OpenSSL 3.x providers.&amp;nbsp; [Ingo Franzki &amp;lt;ifranzki linux.ibm.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Restore SSL dumping on trace7 loglevel with OpenSSL &amp;gt;= 3.0.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Ruediger Pluem, Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mpm_worker: Fix possible warning (AH00045) about children processes not&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; terminating timely.&amp;nbsp; [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.61&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-39884: Apache HTTP Server: source code&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; disclosure with handlers configured via AddType (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A regression in the core of Apache HTTP Server 2.4.60 ignores&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; some use of the legacy content-type based configuration of&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; handlers.&amp;nbsp;&amp;nbsp; "AddType" and similar configuration, under some&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; circumstances where files are requested indirectly, result in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; source code disclosure of local content. For example, PHP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; scripts may be served instead of interpreted.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Users are recommended to upgrade to version 2.4.61, which fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; this issue.&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.60&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-39573: Apache HTTP Server: mod_rewrite proxy&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; handler substitution (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Potential SSRF in mod_rewrite in Apache HTTP Server 2.4.59 and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; earlier allows an attacker to cause unsafe RewriteRules to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unexpectedly setup URL's to be handled by mod_proxy.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38477: Apache HTTP Server: Crash resulting in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Denial of Service in mod_proxy via a malicious request&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; null pointer dereference in mod_proxy in Apache HTTP Server&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.4.59 and earlier allows an attacker to crash the server via a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; malicious request.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38476: Apache HTTP Server may use&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; exploitable/malicious backend application output to run local&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; handlers via internal redirect (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Vulnerability in core of Apache HTTP Server 2.4.59 and earlier&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; are vulnerably to information disclosure, SSRF or local script&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; execution via backend applications whose response headers are&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; malicious or exploitable.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Note: Some legacy uses of the 'AddType' directive to connect a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; request to a handler must be ported to 'AddHandler' after this fix.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38475: Apache HTTP Server weakness in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mod_rewrite when first segment of substitution matches&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; filesystem path. (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Improper escaping of output in mod_rewrite in Apache HTTP Server&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.4.59 and earlier allows an attacker to map URLs to filesystem&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; locations that are permitted to be served by the server but are&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; not intentionally/directly reachable by any URL, resulting in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; code execution or source code disclosure.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Substitutions in server context that use a backreferences or&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; variables as the first segment of the substitution are affected.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Some unsafe RewiteRules will be broken by this change and the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; rewrite flag "UnsafePrefixStat" can be used to opt back in once&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ensuring the substitution is appropriately constrained.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38474: Apache HTTP Server weakness with&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; encoded question marks in backreferences (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Substitution encoding issue in mod_rewrite in Apache HTTP Server&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2.4.59 and earlier allows attacker to execute scripts in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; directories permitted by the configuration but not directly&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reachable by any URL or source disclosure of scripts meant to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; only to be executed as CGI.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Note: Some RewriteRules that capture and substitute unsafely will now&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; fail unless rewrite flag "UnsafeAllow3F" is specified.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38473: Apache HTTP Server proxy encoding&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; problem (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Encoding problem in mod_proxy in Apache HTTP Server 2.4.59 and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; earlier allows request URLs with incorrect encoding to be sent&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to backend services, potentially bypassing authentication via&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; crafted requests.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-38472: Apache HTTP Server on Windows UNC SSRF&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SSRF in Apache HTTP Server on Windows allows to potentially leak&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; NTML hashes to a malicious server via SSRF and malicious&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; requests or content&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Note: Existing configurations that access UNC paths&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; will have to configure new directive "UNCList" to allow access&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; during request processing.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-36387: Apache HTTP Server: DoS by Null&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; pointer in websocket over HTTP/2 (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Serving WebSocket protocol upgrades over a HTTP/2 connection&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; could result in a Null Pointer dereference, leading to a crash&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; of the server process, degrading performance.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Marc Stern (&amp;lt;marc.stern AT approach-cyber.com&amp;gt;)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Fix DNS requests and connections closed before the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configured addressTTL.&amp;nbsp; PR 69126.&amp;nbsp; [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) core: On Linux, log the real thread ID in error logs.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) core: Support zone/scope in IPv6 link-local addresses in Listen and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; VirtualHost directives (requires APR 1.7.x or later).&amp;nbsp; PR 59396&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Reject client-initiated renegotiation with a TLS alert&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (rather than connection closure).&amp;nbsp; [Joe Orton, Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) Updated mime.types.&amp;nbsp; [Mohamed Akram &amp;lt;mohd.akram outlook.com&amp;gt;,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Adam Silverstein &amp;lt;adamsilverstein earthboundhosting.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Fix a regression that causes the default DH parameters for a key&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; no longer set and thus effectively disabling DH ciphers when no explicit&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; DH parameters are set. PR 68863 [Ruediger Pluem]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_cgid: Optional support for file descriptor passing, fixing&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error log handling (configure --enable-cgid-fdpassing) on Unix&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; platforms. PR 54221.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_cgid/mod_cgi: Distinguish script stderr output clearly in&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error logs.&amp;nbsp; PR 61980.&amp;nbsp; [Hank Ibell &amp;lt;hwibell gmail.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_tls: update version of rustls-ffi to v0.13.0.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Daniel McCarney (@cpu}]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_md:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Using OCSP stapling information to trigger certificate renewals. Proposed&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; by @frasertweedale.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Added directive `MDCheckInterval` to control how often the server checks&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for detected revocations. Added proposals for configurations in the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; README.md chapter "Revocations".&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - OCSP stapling: accept OCSP responses without a `nextUpdate` entry which is&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; allowed in RFC 6960. Treat those as having an update interval of 12 hours.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Added by @frasertweedale.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Adapt OpenSSL usage to changes in their API. By Yann Ylavic.&lt;BR /&gt;&lt;BR /&gt;Changes with Apache 2.4.59&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-27316: Apache HTTP Server: HTTP/2 DoS by&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; memory exhaustion on endless continuation frames (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP/2 incoming headers exceeding the limit are temporarily&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; buffered in nghttp2 in order to generate an informative HTTP 413&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; response. If a client does not stop sending headers, this leads&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to memory exhaustion.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Bartek Nowotarski (&lt;A href="https://nowotarski.info/" target="_blank"&gt;https://nowotarski.info/&lt;/A&gt;)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2024-24795: Apache HTTP Server: HTTP Response&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Splitting in multiple modules (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; HTTP Response splitting in multiple modules in Apache HTTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Server allows an attacker that can inject malicious response&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; headers into backend applications to cause an HTTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; desynchronization attack.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; After this change, CGI-like scripts cannot set Transfer-Encoding&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; or Content-Length headers.&amp;nbsp; To restore the ability to set Content-Length&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; header, set per-request environment variable 'ap_trust_cgilike_cl' to any&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; non-empty value.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Keran Mu, Tsinghua University and Zhongguancun&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Laboratory.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) SECURITY: CVE-2023-38709: Apache HTTP Server: HTTP response&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; splitting (cve.mitre.org)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Faulty input validation in the core of Apache allows malicious&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; or exploitable backend/content generators to split HTTP&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; responses.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; This issue affects Apache HTTP Server: through 2.4.58.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credits: Orange Tsai (@orange_8361) from DEVCORE&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_deflate: Fixes and better logging for handling various&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; error and edge cases. [Eric Covener, Yann Ylavic, Joe Orton,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Eric Norris &amp;lt;enorris etsy.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) Add CGIScriptTimeout to mod_cgi. [Eric Covener]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_xml2enc: Tolerate libxml2 2.12.0 and later.&amp;nbsp; PR 68610&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [ttachi &amp;lt;tachihara AT hotmail.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_slotmem_shm: Use ap_os_is_path_absolute() to make it portable.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Jean-Frederic Clere]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Use OpenSSL-standard functions to assemble CA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; name lists for SSLCACertificatePath/SSLCADNRequestPath.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Names will now be consistently sorted. PR 61574.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_xml2enc: Update check to accept any text/ media type&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; or any XML media type per RFC 7303, avoiding&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; corruption of Microsoft OOXML formats.&amp;nbsp; PR 64339.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Joseph Heenan &amp;lt;joseph.heenan fintechlabs.io&amp;gt;, Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_http2: v2.0.26 with the following fixes:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed `Date` header on requests upgraded from HTTP/1.1 (h2c). Fixes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;&lt;A href="https://github.com/icing/mod_h2/issues/272" target="_blank"&gt;https://github.com/icing/mod_h2/issues/272&lt;/A&gt;&amp;gt;.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Fixed small memory leak in h2 header bucket free. Thanks to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Michael Kaufmann for finding this and providing the fix.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) htcacheclean: In -a/-A mode, list all files per subdirectory&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; rather than only one. PR 65091.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Artem Egorenkov &amp;lt;aegorenkov.91 gmail.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: SSLProxyMachineCertificateFile/Path may reference files&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; which include CA certificates; those CA certs are treated as if&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configured with SSLProxyMachineCertificateChainFile.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) htpasswd, htdbm, dbmmanage: Update help&amp;amp;docs to refer to&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "hashing", rather than "encrypting" passwords.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Michele Preziuso &amp;lt;mpreziuso kaosdynamics.com&amp;gt;]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Fix build with LibreSSL 2.0.7+. PR 64047.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Giovanni Bechis, Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) htpasswd: Add support for passwords using SHA-2.&amp;nbsp; [Joe Orton,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) core: Allow mod_env to override system environment vars. PR 63117.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) Allow mod_dav_fs to tolerate race conditions between PROPFIND and an&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; operation which removes a directory/file between apr_dir_read() and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; apr_stat(). Current behaviour is to abort the connection which seems&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inferior to tolerating (and logging) the error. [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ldap: HTML-escape data in the ldap-status handler.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Eric Covener, Chamal De Silva]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Disable the OpenSSL ENGINE API when OPENSSL_NO_ENGINE is set.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Allow for "SSLCryptoDevice builtin" if the ENGINE API is not available,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; notably with OpenSSL &amp;gt;= 3.&amp;nbsp; PR 68080.&amp;nbsp; [Yann Ylavic, Joe Orton]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: Improve compatibility with OpenSSL 3, fix build warnings about&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; deprecated ENGINE_ API, honor OPENSSL_API_COMPAT setting while defaulting&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to compatibitily with version 1.1.1 (including ENGINEs / SSLCryptoDevice).&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_ssl: release memory to the OS when needed. [Giovanni Bechis]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Ignore (and warn about) enablereuse=on for ProxyPassMatch when&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; some dollar substitution (backreference) happens in the hostname or port&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; part of the URL.&amp;nbsp; [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Allow to set a TTL for how long DNS resolutions to backend&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; systems are cached. [Yann Ylavic]&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; *) mod_proxy: Add optional third argument for ProxyRemote, which&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; configures Basic authentication credentials to pass to the remote&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; proxy.&amp;nbsp; PR 37355.&amp;nbsp; [Joe Orton]&lt;BR /&gt;&lt;BR /&gt;[/QUOTE]&lt;/P&gt;</description>
    <pubDate>Fri, 06 Feb 2026 05:33:39 GMT</pubDate>
    <dc:creator>mikeb</dc:creator>
    <dc:date>2026-02-06T05:33:39Z</dc:date>
    <item>
      <title>Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029716#M40058</link>
      <description>&lt;P&gt;My force9 email and website have been migrated to greenby and now the site with the domain ending in force9.co.uk gives 404 "page not found" for all the pages but the domain ending in f9.co.uk works correctly.&lt;/P&gt;&lt;P&gt;I have had no luck trying to get this fixed. A ticket was raised with greenby on 18/11/25. On 20/11/25 they said it would be fixed in 48 hours but it's still not fixed.&lt;/P&gt;&lt;P&gt;All the search engines use the force9 site so this will affect our search ranking.&lt;/P&gt;&lt;P&gt;Does anyone know how I can escalate this? As per the greenby instructions I have asked them to phone me but to no avail.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 10:29:05 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029716#M40058</guid>
      <dc:creator>stourchess</dc:creator>
      <dc:date>2025-11-24T10:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029729#M40059</link>
      <description>&lt;P&gt;I've raised this to the right Plusnet people&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 11:40:40 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029729#M40059</guid>
      <dc:creator>MisterW</dc:creator>
      <dc:date>2025-11-24T11:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029754#M40060</link>
      <description>&lt;P&gt;Thank you very much&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 12:33:09 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029754#M40060</guid>
      <dc:creator>stourchess</dc:creator>
      <dc:date>2025-11-24T12:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029837#M40079</link>
      <description>&lt;P&gt;Just a quick ...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[AOL]&lt;/P&gt;
&lt;P&gt;Me too !&lt;/P&gt;
&lt;P&gt;[/AOL]&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;... to add to list of those allegedly valued customers requiring broken stuff fixing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The plug was apparently pulled on username.force9.co.uk&amp;nbsp; circa 0930 yesterday &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&lt;/P&gt;
&lt;P&gt;Site A-record apparently now has an ENIX IP but homepages still has the usual PN IP &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@7617B13E24C0CCAE119AD01B2BB73839/images/emoticons/rolleyes.gif" alt="Roll_eyes" title="Roll_eyes" /&gt;&lt;/P&gt;
&lt;P&gt;Also username2.plus.com email no longer working as of today - repeated AUTH errors &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&lt;/P&gt;
&lt;P&gt;All other A/Cs webspace/email still working OK ... famous last words and all that &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@0FA1396AC0773F33E2DC472BB4F75D3C/images/emoticons/wink.gif" alt="Wink" title="Wink" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry, no time for any poncing about and/or hoop jumping various at the mo so unable to investigate further.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 06:40:44 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029837#M40079</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-25T06:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029850#M40080</link>
      <description>&lt;P&gt;AUTH errors is that on connection to mail servers or sent message bounce backs?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If on connection that’s likely to be IMAP responsiveness issues&lt;/P&gt;
&lt;P&gt;If sent item bounce backs that’s server reputation - can you please indicate the outbound server cited.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 09:52:43 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029850#M40080</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2025-11-25T09:52:43Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029895#M40082</link>
      <description>&lt;P&gt;I've just got the following response from greenby:&lt;BR /&gt;"&lt;SPAN&gt;The issue should now be fixed, and we apologize for the delay in our response. You can access the page using the following URL:&amp;nbsp;&lt;/SPAN&gt;&lt;A href="http://www.stourbridgechess.f9.co.uk/" target="_blank"&gt;www.stourbridgechess.f9.co.uk&lt;/A&gt;&amp;nbsp;"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Given that the ticket was about&amp;nbsp;&lt;A href="http://www.stourbridgechess.f9.co.uk/" target="_blank"&gt;www.stourbridgechess.force9.co.uk&amp;nbsp;&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;not working, the issue is not fixed. All the search engines use the force9 URL . There are also links to it from many other sites which I have no control over.&lt;BR /&gt;Why can't greenby at least put a permanent redirect in place?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 14:50:43 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029895#M40082</guid>
      <dc:creator>stourchess</dc:creator>
      <dc:date>2025-11-25T14:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029951#M40087</link>
      <description>&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;WEBSPACE FAILURE&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;I now have &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt; *&lt;STRONG&gt;AND*&lt;/STRONG&gt; &lt;A href="http://www.username2.force9.co.uk" target="_blank"&gt;www.username2.force9.co.uk&lt;/A&gt; webspace not working. Using the .f9.co.uk suffix no longer makes any difference either &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@5CA762C7B9B1D4AB36AAB959133ED0B4/images/emoticons/angry.gif" alt="Angry" title="Angry" /&gt;&lt;BR /&gt;&lt;BR /&gt;All resolve to ENIX IPs but homepages still has the usual PN IP. All relevant data still appears to be lurking on homepages, at least for now anyway. I've received several website "up" and "down" notifications recently but the last few entries in the logfile quoted below provides irrefutable evidence of when the problem became very permanent.&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[QUOTE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg5.uptimerobot.com - - [24/Nov/2025:07:22:34 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg10.uptimerobot.com - - [24/Nov/2025:07:27:40 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-fra2.uptimerobot.com - - [24/Nov/2025:07:32:45 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-fsn2.uptimerobot.com - - [24/Nov/2025:07:37:49 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-fra7.uptimerobot.com - - [24/Nov/2025:07:42:55 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg5.uptimerobot.com - - [24/Nov/2025:07:48:00 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-fsn1.uptimerobot.com - - [24/Nov/2025:07:53:05 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg9.uptimerobot.com - - [24/Nov/2025:07:58:09 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg1.uptimerobot.com - - [24/Nov/2025:08:03:14 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg10.uptimerobot.com - - [24/Nov/2025:08:18:29 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg5.uptimerobot.com - - [24/Nov/2025:08:28:38 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg9.uptimerobot.com - - [24/Nov/2025:08:38:48 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg9.uptimerobot.com - - [24/Nov/2025:08:48:58 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;checker-nbg9.uptimerobot.com - - [24/Nov/2025:09:30:01 +0000] "HEAD / HTTP/1.1" 200 - "&lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;http://www.username.force9.co.uk&lt;/A&gt;" "Mozilla/5.0+(compatible; UptimeRobot/2.0; &lt;A href="http://www.uptimerobot.com/" target="_blank"&gt;http://www.uptimerobot.com/&lt;/A&gt;)" &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[no further logfile data of any kind after this point in time]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[/QUOTE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;EMAIL FAILURE&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;PLEASE NOTE:&lt;/STRONG&gt; Typo in previous post - The problem A/C is username2.force9.net plus the standard aliases various of course.&lt;/FONT&gt; &lt;BR /&gt;&lt;BR /&gt;It's POP3 access ONLY, I don't use webmail or IMAP. Always the same error message now despite no changes whatsoever at this end since first being set up when this particular A/C was opened:&lt;BR /&gt;&lt;BR /&gt;Last seen working circa 1724 Hours on 24/11/2025 "Success: You have no new email"&lt;BR /&gt;&lt;BR /&gt;First failure circa 0534 Hours on 25/11/2025 "Server Force9 POP3 rejected your username and password ([AUTH] Authentication failed)"&lt;BR /&gt;&lt;BR /&gt;All subsequent attempts to access this A/C also fail with the same error e.g. circa 1648 Hours on 25/11/2025 "Server Force9 POP3 rejected your username and password ([AUTH] Authentication failed)"&lt;BR /&gt;&lt;BR /&gt;HOWEVER all attempts to access username.force9.net appear to be working as expected, both before and after the migration to Greenby apparently went live. &lt;BR /&gt;&lt;BR /&gt;circa 1724 Hours on 24/11/2025 "Success: new email 1/1 ..."&lt;BR /&gt;circa 0534 Hours on 25/11/2025 "Success: new email 1/1 ..."&lt;BR /&gt;circa 1648 Hours on 25/11/2025 "You have no new email"&lt;BR /&gt;&lt;BR /&gt;Both of these Force9 A/Cs have apparently only just been migrated to Greenby despite PN emails advising that transfers would be commencing in May and June ! All email settings are (and always have been) identical in all respects apart from username and password with no changes whatsoever since first setting everything up when the A/Cs were opened. Both A/Cs are POP3/SMTP using standard ports with servers mail.force9.net and relay.force9.net &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;POP3 SERVER TEST&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[quote]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&amp;gt;telnet mail.force9.net 110&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK POP3 ready &amp;lt;687244345.1764097200@mail.enmail.co&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;user username&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;pass password&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK Logged in.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;list&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK 0 messages:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;quit&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK Logging out.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Connection to host lost.&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&amp;gt;telnet mail.force9.net 110&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK POP3 ready &amp;lt;1450253436.1764097350@mail.enmail.co&amp;gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;user username2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;+OK&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;pass password2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;-ERR [AUTH] Authentication failed.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;Connection to host lost.&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[/QUOTE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;INFO FROM GREENBY PORTAL&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[QUOTE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;username: &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;The migration of your email to Greenby was completed on 20/11/2025. We’ve been keeping your email safe and we’ve also received and stored any new email sent to your Plusnet email addresses since then &lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;username2:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;The migration of your email to Greenby was completed on 20/11/2025. We’ve been keeping your email safe and we’ve also received and stored any new email sent to your Plusnet email addresses since then &lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;[/QUOTE]&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;DATA CHECKED VIA PN PORTAL&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;Usernames and passwords have also been confirmed as being entirely correct by logging into the PN portal and checking the email and webspace settings for each account ! Everything works and appears just fine via both portals but not via Greenby email and web servers. Login failure for POP3 on 1 A/C and #404 for webspace on both A/Cs &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;CONCLUSION&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;I'm very sorry, but there is quite clearly no even remotely plausible excuse for any of these service failures other than finger trouble at the PN/Greenby end &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt; It's all *really* basic stuff which was working and had been working flawlessly (barring F9/PN system/server failures) for donkey's years but now it just suddenly isn't working properly if at all.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/1356"&gt;@Username&lt;/a&gt;.force9.net and &lt;A href="http://www.username.force9.co.uk" target="_blank"&gt;www.username.force9.co.uk&lt;/A&gt; fully operational and in regular use since 4th July 1997&lt;BR /&gt;&lt;BR /&gt;@username2.force9.net and &lt;A href="http://www.username2.force9.co.uk" target="_blank"&gt;www.username2.force9.co.uk&lt;/A&gt; fully operational and in regular use since 27th May 2007&lt;BR /&gt;&lt;BR /&gt;No changes anywhere since day 1. Everything clearly working just fine and dandy until someone pushed the button to finalise the migration of these two historic F9 A/Cs to Greenby leading to several aspects of the service(s) going titsup almost immediately &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@7617B13E24C0CCAE119AD01B2BB73839/images/emoticons/rolleyes.gif" alt="Roll_eyes" title="Roll_eyes" /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It must be clearly understood BY ALL that ...&lt;BR /&gt;&lt;BR /&gt;someone@anyusername.force9.net &lt;BR /&gt;someone@anyusername.force9.co.uk&lt;BR /&gt;someone@anyusername.f9.co.uk&lt;BR /&gt;&lt;BR /&gt;... are equally valid email addresses for the F9 A/C anyusername.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It must also be clearly understood BY ALL that ...&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.anyusername.force9.net" target="_blank"&gt;www.anyusername.force9.net&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.anyusername.force9.co.uk" target="_blank"&gt;www.anyusername.force9.co.uk&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.anyusername.f9.co.uk" target="_blank"&gt;www.anyusername.f9.co.uk&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;... are equally valid URLs for the webspace of F9 A/C anyusername.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If anyone anywhere is even vaguely thinking about moving the goalposts now, several decades after these usernames were issued and started being used in anger, then they really do need to give themselves a bl**dy good slap right now ... then another one in a few minutes time and at regular intervals thereafter just to remind themselves of exactly how stupid and totally unreasonable they're being !!!!! &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This *really* does not bode well for all the much more important A/Cs yet to be migrated &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 04:13:31 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029951#M40087</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-26T04:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029970#M40089</link>
      <description>&lt;P&gt;send me the usernames please, if it's not in the thread.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 09:07:03 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2029970#M40089</guid>
      <dc:creator>plusnettony</dc:creator>
      <dc:date>2025-11-26T09:07:03Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030016#M40091</link>
      <description>&lt;P&gt;This is now fixed ! I discovered the site was working this morning. (The original problem in this thread)&lt;/P&gt;
&lt;P&gt;I'm not sure what encouraged them to fix it but besides this post, I added a message to the greenby ticket "&lt;SPAN&gt;Please can this be escalated. I now wish to make an official complaint" .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I also emailed&amp;nbsp;info@enixltd.com, outlining my poor experience with greenby and with the ticket number.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 15:55:42 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030016#M40091</guid>
      <dc:creator>stourchess</dc:creator>
      <dc:date>2025-11-26T15:55:42Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030099#M40098</link>
      <description>&lt;P&gt;Just a quicky update:&lt;BR /&gt;&lt;BR /&gt;Webspace sort-of working as of early this morning it would appear after some no doubt frantic tweaks various behind the scenes to add a CNAME to the DNS records &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@8BBE3DF35B52AAD1B52BEBDC4974E1AD/images/emoticons/tongue.gif" alt="Tongue" title="Tongue" /&gt; I'll come back and read recent posts later when I find time but this is some important looking stuff that I've discovered so far which may be of interest. It may or may not be covered by posts various above of course but could be of some help to others if not.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;1)&lt;/STRONG&gt; homepages.force9.net should apparently be 91.204.210.11 and &lt;STRONG&gt;NOT&lt;/STRONG&gt; 212.159.8.90 as that's where the website data currently appears to be being served from. It most definitely &lt;STRONG&gt;ISN'T&lt;/STRONG&gt; being served from Ye Olde PN IP that's for sure ! Changes made on homepages have absolutely no effect whatsoever on what's currently being served by Greenby. However, changes made on that particular ENIX IP do &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@0FA1396AC0773F33E2DC472BB4F75D3C/images/emoticons/wink.gif" alt="Wink" title="Wink" /&gt; Use it at your own risk needless to say. &lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;2)&lt;/STRONG&gt; There appears to be a total lack of raw logfiles available on the Greenby server(s) &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&amp;nbsp; That's a show-stopper in my book hence why I've now stopped messing around. No log data then absolutely no use whatsoever to me I'm afraid. It would need to be resolved within a day or two because data will be lost otherwise if archiving is kept the same as F9/PN. I'm not going to be holding my breath waiting for logfiles to (maybe) appear as I rather suspect that they're never going to so it very much looks like time to give up and move on.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;3)&lt;/STRONG&gt; POP3 issues continue and having 'raised' a ticket, even the 'bot' thinks that it's a fundamental Greenby setup issue and recommends raising a ticket to get back-office techies on the job.&amp;nbsp; Ummmmmmmmm, that's what I just did I thought &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@7617B13E24C0CCAE119AD01B2BB73839/images/emoticons/rolleyes.gif" alt="Roll_eyes" title="Roll_eyes" /&gt;&lt;BR /&gt;&lt;BR /&gt;Apart from that, Greenby doesn't look like a bad setup. I'm already an ENIX customer anyway and I'll be moving more stuff over to them very shortly as well. No problems or complaints from me about my mail and web hosting over the past year. Hopefully, those staying with Greenby will have a similar experience once any initial hiccups and issues due to F9/PN silliness and finger-trouble various are sorted out &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@104CD63F9302A50EF5EC70FE32BB8AA1/images/emoticons/smiley.gif" alt="Smiley" title="Smiley" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="5" color="#FF0000"&gt;PN, please sort your DNS out so customers don't have to ponce about second guessing what the IP of essential services needs to be set to in order for it to do what it says on the tin !&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 14:10:30 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030099#M40098</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-27T14:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030107#M40099</link>
      <description>&lt;P&gt;Q: How much do I hate this stupid forum software and it's post editing timeout period ...&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ftp dns 1.jpg"&gt;&lt;img src="https://community.plus.net/skins/images/A0C0974F08C2F141307C5AA348823F1B/responsive_peak/images/image_not_found.png" alt="ftp dns 1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ftp dns 2.jpg" style="width: 545px;"&gt;&lt;img src="https://community.plus.net/t5/image/serverpage/image-id/61904i79EDA1FCF58A96BC/image-size/large?v=v2&amp;amp;px=999" role="button" title="ftp dns 2.jpg" alt="ftp dns 2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A: Almost as much as I hate those who cannot keep their DNS records sensibly up to date so that services at least try to to do what it says on the tin :lol:&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 14:30:44 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030107#M40099</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-27T14:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030138#M40101</link>
      <description>&lt;P&gt;Oh dear, I might have spoken a bit too soon it would appear.&lt;BR /&gt;&lt;BR /&gt;[PANTO]&lt;BR /&gt;&lt;BR /&gt;Ooooo, look it's working ... oh no it isn't ... oh yes it is ... oh no it isn't ...&lt;BR /&gt;&lt;BR /&gt;[/PANTO]&lt;BR /&gt;&lt;BR /&gt;After a day of seemingly all being mostly well, there's just been more ups and downs than a ... [ and I'm quite certain you all know the rest of that one ! ]&lt;BR /&gt;&lt;BR /&gt;#403 all the way on all sites at the mo and a sizable bunch of warning notifications for websites various going AWOL into the bargain &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@6BD5E1FD9194A889D807C8E641344CF1/images/emoticons/sad.gif" alt="Sad" title="Sad" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;PN:&lt;/STRONG&gt; Got that DNS update in hand yet so things don't look quite as stupid as they currently appear to do ?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/26334"&gt;@plusnettony&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;Re POP3 issues. It's username.force9.net working and username2.force9.net not working. Just replace "username" with the actual username of my current PN A/C as registered on this forum.&amp;nbsp; I don't like having personal and very identifiable data posted in public and especially not on a site where it can't ever be redacted in the future. It's been reported to Greenby via ticket system.&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 16:21:37 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030138#M40101</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-27T16:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030149#M40105</link>
      <description>&lt;P&gt;My website has also stopped working both the force9 and f9 URLS give a 403 error!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;I am pretty fed up with all this. I will leave it until tomorrow and then raise another ticket if it's not fixed.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 17:33:32 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030149#M40105</guid>
      <dc:creator>stourchess</dc:creator>
      <dc:date>2025-11-27T17:33:32Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030153#M40106</link>
      <description>&lt;P&gt;Give the guys at Greenby a bit of slack because migrating the entire F9/PN/whatever customer database has to be without any doubt whatsoever a truly monster exercise ! Problems are inevitable. Apart from the sheer volume of data/work involved, the total lack of consistency across the various PN 'brands' and over ~30 years must be a complete nightmare in itself.&lt;BR /&gt;&lt;BR /&gt;I'm sure things will settle down at least a bit in due course ... famous last words and all that :lol:&lt;BR /&gt;&lt;BR /&gt;This is perhaps the first batch of migrations including webspace and therefore all the DNS and server-related issues are coming to light. I've reported the apparent DNS and potential logging issues via the ticket system and noted problems with #403 and #404 errors. It's apparently been escalated. I'll post here if I see/hear/find anything else that seems relevant or interesting &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@104CD63F9302A50EF5EC70FE32BB8AA1/images/emoticons/smiley.gif" alt="Smiley" title="Smiley" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 17:57:30 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030153#M40106</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-27T17:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030166#M40107</link>
      <description>&lt;P&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/415"&gt;@mikeb&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I do not get why you are being so lenient towards Greenby ... frankly they have fouled up big time.&amp;nbsp; I have led sizable migration projects and this is the worst I have seen.&lt;/P&gt;
&lt;P&gt;The existing Plusnet services were a reference base to be replicated...&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Same server IDs&lt;/LI&gt;
&lt;LI&gt;Same login methods&lt;/LI&gt;
&lt;LI&gt;Same domain standards / names&lt;/LI&gt;
&lt;LI&gt;Same email constructs - mailboxes / redirects / aliases / catch all&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;One might have expected of an 'experienced' specialist provider that they would use the same technology stack which they have deployed elsewhere, but no, they have built a brand new untried system into which the working Plusnet services have been migrated. What have been the characteristics of the migration?&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Logon methods are not the same as Plusnet's - that sabotaged the fundamental intent, that from a user's perspective, this should have been a like for like change: things are different - a change to using email address everywhere might have been reasonable ... however ...&lt;/LI&gt;
&lt;LI&gt;Logon requirements for default and secondary email addresses are dissimilar where they were the same with Plusnet&lt;/LI&gt;
&lt;LI&gt;Force9 domains have been morphed to f9&lt;/LI&gt;
&lt;LI&gt;Idps has been morphed to free-online&lt;/LI&gt;
&lt;LI&gt;Aliases did not work&lt;/LI&gt;
&lt;LI&gt;Catchall did not work&lt;/LI&gt;
&lt;LI&gt;The Greenby proxies which direct connections according to an account's migration status do not appear to work consistently&lt;/LI&gt;
&lt;LI&gt;Users are not seeing new emails&lt;/LI&gt;
&lt;LI&gt;Greenby's support appears to be abysmal - poor AI, difficulty speaking to someone who can fix things&lt;/LI&gt;
&lt;LI&gt;Bad advice being provided on configuration changes&lt;/LI&gt;
&lt;LI&gt;Though invited to partake in this forum during the migration, Greenby has yet to become part of the solution to the real issues being experienced by users&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Yes things do go wrong, but when they do, you roll up your selves, dig deep and come to the coal face - Greenby are just not here facing their music.&lt;/P&gt;
&lt;P&gt;PlusNet's support of the email services has at times been challenged, but never have things been as bad as we are seeing from Greenby.&amp;nbsp; Enix claims to be a highly experience competent hosting company: that is not reflected in the Greenby sub-brand.&lt;/P&gt;
&lt;P&gt;The Plusnet guys are doing their very best to get the user experience reported here in front of the Greenby folks ... life would be so much better for all involved, if they just came and participated in this forum.&amp;nbsp; That they have failed to do, so I suggest that they deserve no slack whatsoever.&lt;/P&gt;
&lt;P&gt;I might add that thee really complicated ones (brands) have yet to be started!&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 18:42:32 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030166#M40107</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2025-11-27T18:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030169#M40108</link>
      <description>&lt;P&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/5145"&gt;@Townman&lt;/a&gt;&amp;nbsp;Hope they get their act together before I move, otherwise I shall be forced to move my email provision elsewhere, and that is not something I am looking forward to.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 18:44:16 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030169#M40108</guid>
      <dc:creator>jab1</dc:creator>
      <dc:date>2025-11-27T18:44:16Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030177#M40109</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/5145"&gt;@Townman&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;I do not get why you are being so lenient towards Greenby ...&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Nor me tbh. It's quite unusual to the say the very least !&amp;nbsp; I'm more often than not far from 'understanding' when things go even slightly titsup for no good reason :lol: &lt;BR /&gt;&lt;BR /&gt;But it still has to be a monster job no doubt made 1000x worse by historic F9/PN issues and inconsistency. Just ask BobP how much he still hates me even now for all the grief he got over every single one of the seemingly endless list of historic email, spam filtering and data breach issues over the past 30 years &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@8BBE3DF35B52AAD1B52BEBDC4974E1AD/images/emoticons/tongue.gif" alt="Tongue" title="Tongue" /&gt; I can still show you every single spam message I've received thanks to the (in)famous May 2007 data breach and those that followed shortly after. Upto 20k messages per week per account thanks to total incompetence ! More stats and pretty graphs than I could shake my very best big stick at. All of which demonstrate beyond doubt just how utterly useless every one of the alleged solutions various were in reality despite all the BS and political spin various.&lt;BR /&gt;&lt;BR /&gt;However, contrary to popular opinion no doubt, I'm usually relatively happy to accept sh*t happens once. Maybe even twice. But take the pee and try repeating it more often than that then you can definitely expect bucket loads of sarcasm and being beaten by the biggest stick I can find as regularly as possible until you get all your sh*t sorted properly and to my satisfaction !&lt;BR /&gt;&lt;BR /&gt;You're obviously far more knowledgeable than me in most things and are also clearly on top of all the current issues various that users are experiencing. I haven't been keeping an eye on what's been going on at all I'm afraid. I'm only involved now because things have just gone titsup for me and for no particularly good reason it would seem ! Fortunately, it's all stuff that doesn't really matter in my case. In fact the only significant reason that these F9 A/Cs are being migrated and very closely monitored is as a dry run for the much more important stuff. Forewarned is forearmed and all that.&lt;BR /&gt;&lt;BR /&gt;However, all the historic F9/PN web/mail issues together with more than a few 'hints' over the years about these services being discontinued at some point in time means that I've been moving everything away from PN gradually for several years now. Ideally, I'd like to keep some email addresses and my landline number but it will definitely no longer be anywhere near an end of the world situation if I get totally p*ssed off or financially abused and decide to just storm off in a huff.&lt;BR /&gt;&lt;BR /&gt;At the moment though, Greenby (and to a lesser extent, PN) will get a relatively smooth ride from me if any issues found get fixed in a sensible timeframe. But if that doesn't happen and/or if things get progressively worse then rest assured that I have my very nice collection of really big chunky sticks readily available at arm's length &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@0FA1396AC0773F33E2DC472BB4F75D3C/images/emoticons/wink.gif" alt="Wink" title="Wink" /&gt;&lt;BR /&gt;&lt;BR /&gt;I most certainly can't disagree with any of your comments. It definitely doesn't make good reading all written down in one place does it. It really shouldn't have been that difficult to come up with solution which (almost) 100% matches the current F9/PN/whatever system. Avoiding customer manual intervention of any kind just has to be the goal so if that's not been the case then, like you say, it's been a very poor job right from the start. &lt;BR /&gt;&lt;BR /&gt;I do hope that I'm not giving anyone the benefit of any potential doubt undeservedly &lt;img class="lia-deferred-image lia-image-emoji" src="https://community.plus.net/html/@0FA1396AC0773F33E2DC472BB4F75D3C/images/emoticons/wink.gif" alt="Wink" title="Wink" /&gt; Only time will tell and all that. But my experience so far is actually somewhat better than I feared it would be.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 20:13:13 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030177#M40109</guid>
      <dc:creator>mikeb</dc:creator>
      <dc:date>2025-11-27T20:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030179#M40110</link>
      <description>&lt;P&gt;Mike,&lt;/P&gt;
&lt;P&gt;You have told it how it is over the years … there have been issues, but the service has largely worked. &amp;nbsp;At the moment it is deeply challenged.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Nov 2025 20:56:08 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030179#M40110</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2025-11-27T20:56:08Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030186#M40111</link>
      <description>&lt;P&gt;In reply to&amp;nbsp;&lt;A href="https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030166#M40107" target="_blank"&gt;https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030166#M40107&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;What 'story' was told to Plusnet customers?&lt;/P&gt;
&lt;P&gt;N.B. I took the pain of migrating e-mail away from Plusnet about 2 years ago. That included ditching more than one historic account (web stuff hosted on an e-mail only account? That's a bit strange? Can't complain about it, but it was a bit weird).&lt;/P&gt;
&lt;P&gt;Various failures of sending mail convinced me that not all was well at Plusnet Towers. Given my personal experiences (albeit rather minor), please excuse me if I happen to think the project was going to have its 'gremlins'. Some of which I might think of as zombie gremlins.&lt;/P&gt;
&lt;P&gt;Perhaps Greenby were sold a proverbial pup. It wouldn't be the first time such has happened.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 01:22:14 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030186#M40111</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-11-28T01:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: Website broken following migration to greenby</title>
      <link>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030188#M40112</link>
      <description>&lt;P&gt;That disposition suggests that the issues with Greenby arise from the state of the Plusnet system. &amp;nbsp;It would be interesting to understand how you reach that conclusion.&lt;/P&gt;
&lt;P&gt;The Plusnet systems were functional and have the content to be migrated. &amp;nbsp;Greenby’s task is to mimic that functionality and to accept the transfer of contents. In a multitude of ways their base platform has exhibited fundamental functional deficiencies and inconsistencies. &amp;nbsp;One would not expect such from an established supplier of these services.&lt;/P&gt;
&lt;P&gt;We are though where we are - it’s going to be fix forwards… in Greenby’s world in Greenby’s time frame.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Nov 2025 02:56:48 GMT</pubDate>
      <guid>https://community.plus.net/t5/Everything-else/Website-broken-following-migration-to-greenby/m-p/2030188#M40112</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2025-11-28T02:56:48Z</dc:date>
    </item>
  </channel>
</rss>

