dcret.blogg.se - Burp suite professional error an unknown error occured

#Burp suite professional error an unknown error occured free#

all domains are pointing to the same DocumentRoot.

We observed the same issue with Safari (Desktop and iPhone) on some websites using Debian 10 with Apache. You could also turn off HTTP/2 entirely, but that's probably overkill in most cases. Alternatively, you could issue separate certificates for each domain, but that creates more administrative overhead and may not be worth it. Consult your server's HTTP/2 documentation for more information on how and when it sends HTTP 421. Failing to retry is not particularly user-friendly, but might be desirable for a debugging tool or HTTP library.Įvent #6 is out of your control, but depending on the server's software, #5 may be fixable. The relevant RfC says that the client MAY retry, not that it SHOULD or MUST.

The client does not automatically retry with a new connection (see for example Chrome bug #546991, now fixed).

The server is unable or unwilling to support cross-domain connection reuse (for example because you configured their SSL differently and Apache wants to force a TLS renegotiation), and serves HTTP 421.

The client reuses the connection to make a request for.

This could be done with a wildcard certificate or a SAN certificate.

During TLS negotiation, the server presents a certificate which is valid for both and (and the client accepts it).

The server and client both support and use HTTP/2.

This is caused by the following sequence of events: If this all works, I'll save $ to boot as a bonus and let my Comodo certificates expire in July. I may even try to re-enable the static domains to test.

#Burp suite professional error an unknown error occured free#

I am on a shared host (Webhostinghub) and discovered they now offer free SSL (AutoSSL) that auto renews. So taking the advice, I set about getting separate certificates for each domain.

The article confirmed that it happens in Safari. I did more research and came across another article that talks about it here. However, I was still using a second domain for some of this content and Safari in particular was still giving me problems. I was able to get most of the problems resolved by removing my static domains which served images and javascript. Ok, almost a couple of years later and decided it was time to deal with it. Any help would be appreciated as I am not overly confident they can figure this out. My hosting service has so far been unable to provide anything and requested calling back with the exact time it happens next so they can research it. What I would like to know is if there is anything on the web page (php) coding side of things that can cause this (and can be fixed) or if it is a configuration error or possibly a server error and only my hosting service can fix it. I load pages from one domain and within the page are links to a second domain on the certificate.Įverything I've read regarding this error seems to point to this problem being related to this being a multi-domain certificate.

My servers are Apache on a shared web hosting service so I don't have access to the configuration. I have a PositiveSSL Multi-Domain Certificate from Comodo.

The only pattern I can see is that this may happen When I am redirecting a page using header("Location: ". The next time loading the page will not produce and error and as such the pattern seems pretty random. However, refreshing the browser clears the error and the page loads normally. Host name does not match the Server Name Indication (SNI) in use for The client needs a new connection for this request as the requested I occasionally get the following 421 error: