Search results

Beside the HSTS toggle is a configure link.

That appears to be the preload list which isnt relevant to this fix.

Great that this is now resolved - at least in Obsidian. You can remove HSTS config from nginx config and just use the extension.

To resolve this I had to run /usr/local/psa/admin/sbin/mailmng-outgoing --add-domain --domain-name=migrated-domain.com.au --main-domain-name=subscription-domain.com.au Previously I tried plesk repair mail migrated-domain.com.au which failed with a IntegrityError: NOT NULL constraint failed...

I used the new move domain functionality to move a domain to another subscription. The domain is now missing from the outgoing mail limits database.

Looks like the restore doesnt exit cleanly after an error and just spins its wheels.

Is there a way to discover what tar file a client backup might be located in? I am trying to restore from a multi volume backup but I can see that network activity would suggest that nothing is being downloaded from S3 so it will likely be quicker to grab the SQL backup from the tar file.

I think it was SSL it but Ive made so many changes on this server now that I dont recall exact details Im afraid.

Its a known issue Resolved - SSL It - HSTS appearing twice in headers

I've only upgraded 1 server with a dozen sites on it to see how things go. No show stoppers so far but a few annoyances.

Check your repo sources, I imagine Plesk just pulls latest from them.

Advisor states HTTP/2 isnt enabled, HTTP/2 is running all sites on this server. Pressing "Enable" does nothing

Updated to 18.0.19 and selected an existing cert for a domain, upon applying it locked the subscription. What controls this in the service plan?

The SSL It issue with doubled up HSTS headers is a bug - EXTSSLIT-462

Is there a way of getting only changed files to deploy instead of slam dunking the entire repo over the top of the deploy directory? Thanks Dave.

Any update on this? Also, where do we track Plesk bugs?

Was update 57 pulled or something, I get this across all servers. E: Failed to fetch http://autoinstall.plesk.com/ubuntu/PSA_17.8.11/dists/xenial/all/binary-amd64/Packages.gz Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. Warning...

Wordpress Core gets updated, you just get "Selected items were updated with errors:" notice so clients panic a bit.

I get this warning when upgrading Wordpress Core via the GUI. On 17.8.11 Plesk and 4.1.0-1971 of the toolkit. PHP Warning: Declaration of WP_CLI\CoreUpgrader::download_package($package) should be compatible with WP_Upgrader::download_package($package, $check_signatures = false) in...

I enabled the SSL It extension on another site to test the previous issue I had with HSTS (same problem). I also then noticed that the service plan is locked for sync for that subscription - is this intended?