Search results

I know the title sounds a little misleading, but I didn't know how else to describe it shortly. Here's my dilemma, I have a few IP addresses on my server and the Plesk interface binds to port 8443 on all of them. I'd like Plesk to only respond to port 8443 on the server's primary IP address...

So, I was just notified by a client of mine that when he attempts to access a domain ending in dot (domain.com.) will load the site, but then browsers will throw up an SSL error as the certificate does not match the domain. In my case, it's returning the default server Plesk cert instead of the...

Well, I figured out the issue. It's the Atomic PHP repo... I removed it, regenerated the config files and it works fine now. So problem solved.

As far as I can determine, I'm running the stock config + Atomic PHP repo. It's just that it's complaining about vhost config issues, I've checked them and everything points to all the right directories and the files are there... Guess I'll rebuild everything by hand and upload all my clients'...

Howdy UFHH01, I'm running CentOS 6.7, but I just did a full erase and reinstall. So no issues at the moment... EDIT: Found out what my issue was, Atomic PHP Panda was breaking something apparently. So I removed it and regenerated the vhost files and now it works.

Well... I'll add my error problems into this thing too. After restoring a backup made prior to the update, I still encounter some odd httpd issue regarding vhosts, even after attempting a repair. [[email protected]] /usr/local/psa/bin #> /usr/local/psa/bin/repair --run -- Restoring DNS server...

Howdy folks, I've been in and out the forum a few times in the last 2 years or so finding fixes for issues I've had, but this is the first time I've registered and posted anything here, so here goes! I'm curious if other folks have been having issues with the last few updates? I was using the...