A critical vulnerability (CVE-2019-10149) was found in Exim mail server. It allows to execute some code on victim's server with root privileges. This vulnerability affects versions from 4.87 to 4.91. If you are using Exim and haven't ordered managed service, you should urgently upgrade your version of Exim to 4.92.
(UA-Hosting)
(UA-Hosting)
How to prevent vestacp from filtering certain domains and providing default content/ssl
-
PiggyPiglet
- Posts: 1
- Joined: Tue Jan 23, 2018 3:56 pm
- Os: Ubuntu 16x
- Web: apache + nginx
How to prevent vestacp from filtering certain domains and providing default content/ssl
NOTE: Using Ubuntu 16.04
I'm trying to install Pterodactyl Panel alongside vestacp, but I'm encountering an issue with vestacp interfering. I've installed all the files into /var/www/pterodactyl as the documentation of Pterodactyl encourages, and I've made the vhost (ssl was generated with vestacp's letsencrypt) in /etc/nginx/conf.d.
What I believe the issue is, is that vestacp is detecting the domain as "unregistered", since it's not apart of any vestacp account, and then is trying to show the default vestacp content. I believe the pterodactyl vhost is working somewhat, since the force https part is working, but vesta's vhost is overriding the rest.
tl;dr: I'm asking how can I make vestacp ignore a specific domain so my custom vhost in /etc/nginx/conf.d can work as intended, or even better, disable showing default content for non registered domains entirely.
I'm trying to install Pterodactyl Panel alongside vestacp, but I'm encountering an issue with vestacp interfering. I've installed all the files into /var/www/pterodactyl as the documentation of Pterodactyl encourages, and I've made the vhost (ssl was generated with vestacp's letsencrypt) in /etc/nginx/conf.d.
What I believe the issue is, is that vestacp is detecting the domain as "unregistered", since it's not apart of any vestacp account, and then is trying to show the default vestacp content. I believe the pterodactyl vhost is working somewhat, since the force https part is working, but vesta's vhost is overriding the rest.
tl;dr: I'm asking how can I make vestacp ignore a specific domain so my custom vhost in /etc/nginx/conf.d can work as intended, or even better, disable showing default content for non registered domains entirely.