Recent content by squorpeeon

Installed AWS Plesk AMI (BYOL) and need to run node.js 4.7. I see 6.9 and 7.4 installed. Any way to add another?

I can't help you with the forward but don't waste your time on JXCore. Development has ceased. http://www.nubisa.com/nubisa-halting-active-development-on-jxcore-platform/

I can't seem to find a way to upgrade licenses anymore. For instance from Web Admin to Web Pro. I do see where I can cancel but no other options. Is it now required to just purchase a new license? What if I bought a license only one day ago and want to upgrade?

Sorry I have no other advice since I'm on CentOS. I'm running 12.5 with no issues, maybe an upgrade is in your future? Backup, backup, backup is my last words of advice. Hope you get it resolved.

I use the Route 53 extension and it works great however most of the domains I host use Google Domains DNS. When I create a new domain that won't use Route 53 I have to turn off DNS and then delete the zone from Route 53 manually. Is there some back end way to create a service plan that has DNS...

Which version of Plesk are you using. There is a bug in 12 that requires a quick fix. 12.5 should work fine. For 12 you can try running the following. It worked for me on CentOS 7. A restart is probably required but I am not sure. sudo /usr/sbin/update-alternatives --set mta /usr/bin/msmtp

You just jogged my memory. Nginx is installed as a reverse proxy by default. My problem was with nginx, it would occasionally crash and port 80 traffic would not get served. That is when I did a fresh install rather than tracking down the issue with nginx crashing. I haven't had any issues since...

I just created a snapshot and reverted to it with no issues. It makes me think it is something in the EC2 config and not in the volume. Have you tried creating a new security group and using it just to be sure it isn't a firewall issue? I don't use any firewall on my installs other than Security...

Unfortunately in my case I had not yet created a snapshot to revert to. You make a valid point though. I think I will test that.

I know this is no help but I had a similar situation on my AWS install. I could access :8443 but nothing on :80. I thought it was a firewall issue but ruled that out both on the server and in the Security Group. I then figured that AWS blocked my port 80 as I read that happens to some users and...

Thanks. Your workaround works great.

Quick update. I tried the recommended CentOS 7 with the same result. Can anyone confirm that installing Plesk 12 without a mail server and using the msmtp relay option actually works?

Ah, intersting. In that case I'll just wait for 7.1 support. Other than panel notifications not working the setup is fast and rock solid. I don't sell web hosting either so I can wait.

Just for the heck of it I fired up a fresh instance on Digital Ocean and another on Linode. Same result, unable to send mail.

I'm getting somewhere and nowhere really fast. This KB was really helpful finding the log files, http://kb.odin.com/en/111283. The ones I found aren't very descriptive. [2015-04-08 15:00:47] ERR [panel] Unable to send mail. [2015-04-08 15:00:47] ERR [panel] Error sending the report: Unable to...