• Resolved michaelmartin73

    (@michaelmartin73)


    Hello guys,

    I wondered if you could perhaps please shed some light on an issue I’m facing.

    I have an EasyWP package from Namecheap. It’s up and running (well, mostly) and I am working through various things that need sorting like 301 redirects. I set one up within the Namecheap dashboard, but it got mysteriously deleted. I set it up again and the same thing happened. So I got in touch with Namecheap who, after a 2 hour long live chat (!!!) of my repeatedly explaining what had happened and asking how to resolve, and being passed from one customer service agent to another, they finally told me it’s not possible to do this. Despite my asking why, they did not give me an explanation.

    Anyway, using https://redirectcheck.com to test it seems that the following urls trigger a 301 redirect:

    https://www.reclaimdesign.org
    https://reclaimdesign.org
    https://www.reclaimdesign.org

    However, this one triggers a 200:

    https://www.reclaimdesign.org

    HTTP/2 200
    date: Wed, 12 Feb 2020 18:59:58 GMT
    content-type: text/html; charset=UTF-8
    content-length: 89661
    vary: Accept-Encoding
    x-ua-compatible: IE=edge
    link: ; rel="https://api.w.org/"
    link: ; rel=shortlink
    x-frame-options: SAMEORIGIN
    x-content-type-options: nosniff
    x-xss-protection: 1; mode=block
    cache-control: public
    referrer-policy: strict-origin-when-cross-origin
    x-cacheable: YES
    age: 1356
    x-cache: HIT
    accept-ranges: bytes
    https: on

    I have a valid SSL certificate installed (also bought from Namecheap).

    In my research on how to fix this problem myself, I came across a mention of your plugin, and I wanted to ask if you think it will resolve this (before installing it – I’m increasingly nervous of installing new plugins because in the last few weeks I have experienced several odd issues that were lengthy to fix as a result).

    Many thanks for your assistance.

    Michael.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Mark

    (@markwolters)

    Hi Michael,

    the https://www domain returning a 200 code is correct. Since the site is already on https://, it doesn’t have to be redirected to https://. Therefore an OK status code (200) is returned.

    There are some resources on your site not loading correctly when visiting over https://www. This happens because you have a security header (Access-Control-Allow-Origin) that only allows some resources to load on https:// without www. To fix this you can either update the policy (which can usually be found in your .htaccess file) to include https://www, or add a redirect from https://www to https://.

    Let me know if you have any other questions.

    Mark

    Thread Starter michaelmartin73

    (@michaelmartin73)

    Hi Mark,

    Thank you very much for your reply, and assistance. Unfortunately Namecheap do not allow access to the .htaccess file. Is there another way I could try?

    Michael.

    Plugin Author Mark

    (@markwolters)

    Does Namecheap have control panel where you might be able to adjust these settings? If not, you might have to contact them to make any changes.

    Mark

    Thread Starter michaelmartin73

    (@michaelmartin73)

    Hi Mark, they do, but when the details get entered for a redirect they promptly get deleted! I have spoken to them (I spent 2 hours in a live chat with them last night), but they couldn’t tell me why that was happening and the end result of the chat was that they told me it wasn’t possible and that I should add this code to the header of my site:

    
    <script type="text/javascript">
    if ( document.domain.substring(0,4).toLowerCase() == 'www.' ) {
    window.location = document.URL.replace("//www.","//");
    }
    </script>

    Does it make sense to do that? I’m not very experienced with this stuff. I can add the code no worries, but am not sure of any ramifications.

    Many thanks for your help.

    Michael.

    Plugin Author Mark

    (@markwolters)

    It can be possible to do it via Javascript but this is definitely not the recommended way. The .htaccess file is the recommend place to do this. Javascript is not as reliable as the .htaccess file. A control panel like cPanel is a good alternative to add redirects.

    Mark

    Thread Starter michaelmartin73

    (@michaelmartin73)

    Thank you Mark

    Thread Starter michaelmartin73

    (@michaelmartin73)

    Hi Mark,

    I have another question please! I had previously downloaded the SSL plugin and clicked activate, but stopped when it asked me to confirm (I can’t remember the exact wording and the screen is no longer visible. At that point I clicked deactivate and I emailed the above message.

    I am just checking Site Health and it says:

    You are accessing this website using HTTPS, but your WordPress Address is not set up to use HTTPS by default.

    Read more about why you should use HTTPS (opens in a new tab)

    Update your site addresses

    This error message wasn’t visible yesterday when I last looked at Site Health, so I guess it must have something to do with the plugin perhaps? I’m not sure of anything else that has changed. It’s the only thing I can think of. Please could you advise how I can resolve it? Many thanks for your help.

    Plugin Author Mark

    (@markwolters)

    When Really Simple SSL has been deactivated via the plugins overview your site will be reverted to https://. You can still access the site over https:// but accessing it over https:// will show this message. Activating Really Simple SSL will show the ‘Go ahead, activate SSL!’ notice again. Pressing that will move your WordPress address to https:// and remove the warning from your site health screen.

    Thread Starter michaelmartin73

    (@michaelmartin73)

    Thank you Mark. I went in to Settings and updated the wordpress url and site url to https://reclaimdesign.org and the message seems to have now gone away. I got panicked that the site was broken, since RankMath would no longer allow me to update (which led me to check the Site Health messages). That also seems to be working again – phew. Thank you for your quick reply – I appreciate it.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘EasyWP SSL Query’ is closed to new replies.