Secure Connection Warning

url9839.postmymeds.co.uk doesn't support a secure connection
You are seeing this warning because this site does not support HTTPS and you are in Incognito mode. Learn more about this warning

The warning you're seeing indicates that the website `url9839.postmymeds.co.uk` does not support HTTPS (secure connection), which is likely why you're encountering issues in Incognito mode. Browsers often restrict access to non-secure sites in this mode for privacy and security reasons.

Here are a few steps you can take to resolve the issue:

1. **Check Site Configuration**: Ensure that the site is configured to support HTTPS. This typically involves installing an SSL certificate.

2. **Access via HTTP**: If you trust the site and it's intended to be accessed over HTTP, you can try typing `http://url9839.postmymeds.co.uk` in the address bar instead of the default `https://`.

3. **Browser Settings**: If you're in Incognito mode and still need to access the site, try switching to a regular browsing window. However, be cautious with sensitive data when using non-secure sites.

4. **Contact Site Administrator**: If you are the administrator of the site, consider enabling HTTPS by obtaining an SSL certificate from a certificate authority (CA).

5. **Use Different Browsers**: Sometimes, different browsers have varying levels of security enforcement. Testing the site on another browser might yield different results.

If you need further assistance or details on how to implement HTTPS, let me know!

postmymeds.co.uk this has ssl support

User's site `postmymeds.co.uk` has SSL support.

If `postmymeds.co.uk` has SSL support but you're still encountering issues with `url9839.postmymeds.co.uk`, here are some possible reasons and solutions:

1. **Subdomain SSL Configuration**: Ensure that the SSL certificate covers the subdomain `url9839`. Some SSL certificates are only valid for the main domain (`postmymeds.co.uk`) and do not include subdomains. You might need to obtain a wildcard SSL certificate or specifically add the subdomain to your existing certificate.

2. **DNS Settings**: Check your DNS settings to confirm that the subdomain is correctly pointing to the server that has the SSL certificate installed.

3. **Server Configuration**: Ensure that the server (e.g., Nginx, Apache) is configured to serve the subdomain over HTTPS. This includes having the correct virtual host settings that listen for SSL connections.

4. **Mixed Content Issues**: If the site uses HTTPS but some resources (like images or scripts) are still loaded over HTTP, modern browsers may block these resources, leading to security warnings. Check for mixed content issues in the browser console.

5. **Incognito Mode Restrictions**: While HTTPS should generally work in Incognito mode, some browsers may be stricter. Testing in a regular window can help determine if this is a browser-specific issue.

6. **Clear Cache**: Sometimes, cached data can cause issues. Clear your browser's cache and cookies and try accessing the site again.

If you continue to experience problems, providing any specific error messages or behavior can help narrow down the issue further.