Vesta Control Panel - Forum

Yes, I ran the resolvconf command and restarted resolver. *My* nameservers shows up just fine. But so do 8.8.8.8 and 8.8.4.4, and they're not in the head or base files. There's no tail file. I just don't know where it's getting the 8.8. entries from.

chattr isn't working for me:
chattr: Inappropriate ioctl for device while reading flags on resolv.conf

I'm running Ubuntu 16.04 and /etc/resolv.conf is a link to ../run/resolvconf/resolv.conf

The good news is that I can just edit every time I reboot, but it'd be nice to not have to.

resolv.conf gets rebuilt at reboot. How can I set the name servers in resolv.conf so they're permanent?

For the life of me, I can't find where it gets 8.8.8.8 and 8.8.4.4. from on Ubuntu 16.04.

I've edited /etc/resolvconf/resolv.conf.d/base, so it puts my desired nameservers before the Google ...

So…should I run sa-learn as root and have it scan various users' .Spam folders, or should I run this as each VestaCP user?

If I run it as each individual user, does sa-learn --sync sync each user's bayes data to a central SpamAssassin database?

I'm running Ubuntu 16.04 LTS and it gives me PHP 7.0

skurudo wrote: Please uncheck ssl checkbox -> save and add ssl support and let's encrypt.

That did it. Thanks!

Thank you for the reply.

I updated the templates and rebuilt web for one user. That user still doesn't have a conf_letsencrypt file.

In the panel for that user's domain, SSL is checked, but Let's Encrypt is not. The SSL cert shows up in the boxes below.

If I check the Let's Encrypt box and click ...

I use the force http template, and it's been working on my Let's Encrypt sites.

However, doing a file search for "conf_letsencrypt" only turns up two files: My default domain, and one other domain. My 9 or so other sites don't have the conf_letsencrypt files.

What do I need to do to rebuild my ...

I've not tried this, but a cursory look shows it's using iptables:

iptables -L will show you what you have set.

Here's something I found that's supposed to open 443:

iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
service iptables save
service iptables restart