Dimitar Terziev

Hello @gemini23,

You are experiencing this issue because the HTTP PUT requests are blocked in your .htaccess file by the 6G firewall rules:

# 6G:[REQUEST METHOD]
<IfModule mod_rewrite.c>
        RewriteCond %{REQUEST_METHOD} ^(connect|debug|delete|move|put|trace|track) [NC]
        RewriteRule .* - [F]
</IfModule>

Thus, the following plugin’s request has failed with 403 – Forbidden error:

PUT https://www.londontheatre1.com/wp-json/siteground-settings/v1/update-settings
Status 403 Forbidden

I would advise you to modify the .htaccess rules of the affected sites and allow the HTTP PUT requests, such as:

# 6G:[REQUEST METHOD]
<IfModule mod_rewrite.c>
        RewriteCond %{REQUEST_METHOD} ^(connect|debug|delete|move|trace|track) [NC]
        RewriteRule .* - [F]
</IfModule>

Best Regards,
Dimitar Terziev

Hello @pilartorrendell,

The SiteGround Migrator plugin is not suitable for migrating WordPress sites hosted on a local environment. Instead, you should manually transfer your website to your SiteGround account by uploading the files using an FTP client (such as FileZilla, for example) and importing the database using your Site Tools -> PhpMyAdmin tool.

You may want to check our comprehensive tutorial, which describes this process thoroughly:

How to Transfer WordPress Manually

Best Regards,
Dimitar Terziev

Hello @calibercooling,

Such notification is displayed on the last step of the transfer:

Update your DNS

Please change the NS of your domain. Note that these changes require up to 48 hours of distribution time. Do not modify your site during this period to avoid data loss.

Still, if you do not wish to wait for the DNS propagation period to pass and would like to make changes to the transferred site, you can use the temporary URL that is generated after the transfer is completed.

Best Regards,
Dimitar Terziev

Hello @hellothere2022,

Please follow the same instructions provided by my colleagues above and try disabling the CSS, JavaScript and HTML optimizations one by one from your Dashboard > SG Optimizer > Frontend menu and check if one of them does not interfere.

If this is the case, you can leave this particular setting disabled and still take advantage of the rest of the features offered by the plugin.

If there is no difference, please provide us with the domain name of the affected website and the steps we should take to replicate the problems that you encountered.

Best Regards,
Dimitar Terziev

Hello @hellothere2022,

I am sorry to hear you are facing such issues with the plugin.

Please try disabling the CSS, JavaScript and HTML optimizations one by one from your Dashboard > SG Optimizer > Frontend menu and check if one of them does not interfere.

If this is the case, you can leave this particular setting disabled and still take advantage of the rest of the features offered by the plugin.

If there is no difference, please provide us with the domain name of the affected website and the steps we should take to replicate the problems that you encountered.

Best Regards,
Dimitar Terziev

Hello,

If you are Siteground customer, please open a ticket with us and provide your login details there.

Otherwise, you can create and password protect a test page with simple login details (such as test/test) and provide us with a direct link to this page, so we can check it further.

Best Regards,
Dimitar Terziev

Hello David,

I tested both sites where the SG Security plugin is active, and saw no degraded performance. I also believe that the reported issue is not directly related to the plugin.

If you still see 500 errors while logging in, please open a ticket with SiteGround and provide your login details there, so we can investigate it further.

Best Regards,
Dimitar Terziev

Hello @anzach,

The W3C validator will trigger this error if sizes attribute is set but srcset is not. I was unable to replicate it on my end.

Could you please provide us with your site’s URL, so we can take a closer look on this?

Best Regards,
Dimitar Terziev