-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmdeploy run issues [Contabo] #515
Comments
For the sysctls: Contabo is dropping their settings into the bottom of |
In general I think we should also advise against using contabo in the README. These errors didn't seem to come up consistently for all contabo VPSs, right? So we can catch some of them, but I'm not convinced we should clean up their mess of breaking Debian 12. |
if you are going to do so, also mention that Contabo limits traffic volume in port 25 and eventually you might need to try to convince support of rising limit (which I have failed so far) |
On Tue, Mar 11, 2025 at 05:08 -0700, adb wrote:
adbenitez left a comment (chatmail/server#515)
> In general I think we should also advise against using contabo in the README. These errors didn't seem to come up consistently for all contabo VPSs, right? So we can catch some of them, but I'm not convinced we should clean up their mess of breaking Debian 12.
if you are going to do so, also mention that Contabo limits traffic volume in port 25 and eventually you might need to try to convince support of rising limit (which I have failed so far)
Maybe we can do a chatmail.at/hosting-notes.{md,html} file that has alphabetical sorted
notes on various hosters? Could start with just some .md file on current repo here.
|
A user reported problems trying to deploy a server on a Debian 12 Contabo VPS and I ordered one to reproduce the problems. Here is what I found doing a clean deployment.
The README should tell users to set the
www
andmta-sts
CNAMEs before the first run of cmdeploy to avoid having to hit those errors.Contabo ships broken DNS servers in
/etc/resolv.conf
. This really messes with the deploy in several ways. I think it would be wise to immediately overwrite the system DNS recursors with known good ones (google/8.8.8.8, opendns, etc. something that just works until Unbound is running)Extremely early in the cmdeploy run it needs to start checking and managing some sysctls. Contabo ships
net.ipv6.conf.all.disable_ipv6=1
which prevents Unbound from working after it is installed because it cannot bind to::1
. We can just drop a file into/etc/sysctl.d/
and actually there are some important things that should be changed for hardening the TCP/IP stack that can be discussed at another time. Having a functional IPv6 stack is important regardless of whether or not we intend to use it because of these little issues.opendkim-genkey
fails because it is being run as useropendkim
and/usr/sbin
will not be in the PATH. The command should be updated to use the absolute path:/usr/sbin/opendkim-genkey
After these changes are made the deployment work successfully.
The text was updated successfully, but these errors were encountered: