Search results

No issues here, but had to manually restart apache.

Just updated my question -- it does work. I didn't check the STATISTICS tab after the migration but noticed the site was restricted in size and bandwith. The command above solved this issue. I'll close the thread. Hopefully this helps someone else that experiences this. BTW, lovin' Onyx.

Just found this for Plesk 12.5 > plesk bin subscription --switch-subscription example.com -service-plan Unlimited Will this fix the email issue limit we're having on Plesk Onyx?

Using the migration tool we were able to migrate from 12.5.30 (update 51) to Onyx 17.0.17 (update 4). However, the 12.5 server (both use Web Admin edition) had our domain email at default: unlimited. Under Onyx 17.0.17 the email is set to default: 100 meg. Searching the forums and the net...

Mario, check your GMail spam folder. Without SPF, PTR and DKIM turned on, our mail was ending up in spam folders, and we don't have a mailing list -- Google and Yahoo were just low-scoring our email without these things. If you do or don't see your forwarded email in the GMail spam folder, run...

Moving from an SSD server with Plesk 12.5.50 installed to a new cloud server. What would be the best way to migrate: A) Create the new server and install Onyx, configure the server (MariaDB, NGINX etc) and the move the websites and email by hand or B) Create the new server, migrate the...

I'm Confused @UFHH01 -- DKIM is signing all our outbound PHP mail in Plesk 12.5 with CentOS 6.8, which is why our site's email to GMail and Yahoo get through (along with SPF and DMARC signing), so this is something that doesn't work in Onyx? We're about to upgrade to Onyx and this would be a...

I've got a older server running 12.5 that I used the Atomic repo on and they've not upgraded MySQL since August (it's on 5.5.51-35.el6.art.x86_64.rpm). I'll never make this mistake again and use the OS repo. Can I simply turn off the Atomicorp repo and the Plesk repo will upgrade this version...

Agreed. Not getting an email on either email address with an activation key. Absolutely going nuts waiting for the amazing advancements in Onyx!!

As a text record you copy a part of the contents from the file /etc/opendkim/keys/yourdomain.com/mail.txt (or default.txt), it data should start from v=DKIM1; k=rsa; to the end, without the quotes as you can see it’s in quotes. It'll look like this example: v=DKIM1; k=rsa...

It should install automatically when you install PHP in Plesk 12.5 If IonCube isn't loaded, log into your server using SSH and run the following commands: wget -q -O - http://www.atomicorp.com/installers/atomic | sh yum update php-ioncube-loader

Yup, can confirm. Just built a server with CentOS 6.8 and the current version of Plesk -- flawless. Thanks for notifying us of the update Igor!! :)

Lloyd, I apologize if I'm not communicating my point... I have read and see exactly what you're saying, however the issue I mention directly involves only Chrome 51 stable(incl further versions), the most used browser worldwide, and Plesk/Centos/NGINX. Plesk wrote: What about ALPN Support...

Exactly -- Plesk users would need to use Ubuntu, but we use Plesk with CentOS 6.7 on our servers. We're stuck without a path to http2 unless we switch all our servers over to Ubuntu. :(

Hi Lloyd -- According to NGINX, we also need OpenSSL 1.0.2, so unless we're running Plesk with Ubuntu 16.04 LTS (which uses OpenSSL 1.0.2), having ALPN added to NGINX still doesn't help us with http2 Chrome 51 users. They'll be downgraded to http/1. Seems that based on the NGINX site, the new...

Looks like Google has chosen to stop supporting NPN for all Chrome 51 users, so even if we've upgraded our sites to http2, since we're still using NPN rather than ALPN, due to the OpenSSL version, Chrome will downgrade our site to an http/1 connection. Full details and explanation from NGINX...

For complete results, try your url here > https://tools.keycdn.com/http2-test HTTP/2 Test Result chatme.im Yeah! chatme.im supports HTTP/2.0. ALPN supported. Looks like you're good to go. Ignore the browser error.

Please correct me if I'm wrong, but it seems that the ALPN issue has been addressed in openssl 1.0.1t - https://www.openssl.org/news/openssl-1.0.1-notes.html If so, would it be possible for Plesk to update us to 1.0.1t or post an update method for those of us that use nginx with HTTP/2?