I'm running OpenVPN on an Ubuntu server.
When I try to start nginx now, it throws error:
'sudo: unable to resolve host ip-xxx-xx-x-xxx'
I realize this is b/c the routing has changed but how can I get it to continue to start up even when on OpenVPN?
I have a Ubuntu 16.04 server running OpenVPN (via UPD).
This works great, except once it connects to VPN, I get kicked out of the SSH connection, and the DNS/http connections no longer resolve.
This is as expected, but how do I still keep those connections working while having the server's outbound requests go through the VPN?
I have an Ubuntu EC2 instance that I SSH in via ssh keypairs.
When I try to restart systemd it prompts for a password, which I don't have. I don't believe I set one up, and I have no idea what it would be, since I'm using the keypair to connect as the ubuntu user:
ubuntu@ip-172-31-35-37:~$ systemctl daemon-reload
==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: Ubuntu (ubuntu)
Password:
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
==== AUTHENTICATION FAILED ===
Failed to execute operation: Access denied
How can I make this work?
I just moved a site from one domain to another. It's still on the same servers behind an AWS Elastic Load Balancer. I also changed the certificate on the load balancer to one for the new domain.
The problem is that all existing links out there are to https://www.old-domain.com -- so when they hit the load balancer, the SSL handshake fails, so it doesn't redirect (b/c the certificate is no for http://newdomain.com)
I'm trying to figure out my options for how to redirect the https links from the old domain. It looks like the best options are either:
Get a Subject Alternate Names (SANs), put all the domains on there, and redirect the old domains in the NGINX conf. But, this is expensive!
Renew the certificate for the https://old-domain.com and have that on a separate IP and redirect there. But that means another EC2 instance, right? Meh.
This posts seems to talk about another solution, but I haven't made enough sense of it yet: Scaling Multiple SSL Domains on Multiple EC2 instances in AWS ELB
Suggestions on the best way to do this?
I appreciate it!
I can't seem to get dovecot to start. My log keeps showing this stuff:
connect from localhost[127.0.0.1]
Mar 1 17:15:01 mac postfix/smtpd[32526]: warning: SASL: Connect to private/auth-client failed: No such file or directory
Mar 1 17:15:01 mac postfix/smtpd[32526]: fatal: no SASL authentication mechanisms
Mar 1 17:15:02 mac postfix/master[21369]: warning: process /usr/lib/postfix/smtpd pid 32526 exit status 1
Mar 1 17:15:02 mac postfix/master[21369]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Mar 1 17:15:03 mac postfix/smtpd[32546]: connect from localhost[127.0.0.1]
Mar 1 17:15:03 mac postfix/smtpd[32546]: warning: SASL: Connect to private/auth-client failed: No such file or directory
Mar 1 17:15:03 mac postfix/smtpd[32546]: fatal: no SASL authentication mechanisms
Mar 1 17:15:04 mac postfix/master[21369]: warning: process /usr/lib/postfix/smtpd pid 32546 exit status 1
Mar 1 17:15:04 mac postfix/master[21369]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
My /etc/postfix/main.cf has:
home_mailbox = Maildir/
mailbox_command =
inet_protocols = ipv4
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth-client
smtpd_sasl_local_domain =
smtpd_sasl_security_options = noanonymous
And googling makes it look like I need to add a client block like:
client {
path = /var/spool/postfix/auth/dovecot
mode = 0660
user = postfix
group = mail
}
But it seems that dovecot has been changed since all the examples I find, so I'm not sure where to put that. I'm using Dovecot 2.0.13
Any ideas how to fix this? Thanks!
I have a monit script that checks that nginx is up and running. One thing it does is checks for a file 'ping.txt'. I can view it in the browser, but what would cause the script to get a 301 redirect response back?
monit script snippet:
if failed port 80 protocol http and request '/ping.txt'
Here's what's in the nginx log:
127.0.0.1 - - [29/Feb/2012:20:59:58 +0000] "GET /ping.txt HTTP/1.1" 301 185 "-" "monit/5.2.5"
How do I redirect an request at www. to the non-www version?
This should include requests to the root domain as well as any (wildcard) subdomain.
I also don't want any unnecessary if statements, as per the nginx pitfalls document.
Here's what I have so far but it only seems to work for the root domain, not subdoamins.
server {
listen 80 default_server;
server_name www.*;
rewrite "^www\.(.*)" $scheme://$1 permanent;
}
Monit seems to be working, but when I go to the web interface at port :2812 I get:
Not Found
There is no service by that name
monit 5.2.5
--
But again, things appear ok on the CLI
-->:/var/log$ sudo monit -t
Control file syntax OK
-->:/var/log$ sudo monit status
The Monit daemon 5.2.5 uptime: 11m
System 'system_mydomain.net'
status running
monitoring status monitored
load average [0.00] [0.01] [0.05]
cpu 0.0%us 0.0%sy 0.0%wa
memory usage 645520 kB [63.4%]
swap usage 213128 kB [10.1%]
data collected Wed Feb 15 06:27:26 2012
Any ideas?
Most of the time when I reboot my Ubunutu server, I get "Waiting for Redis to shutdown…" over and over and it never stops until I force reboot. What could cause this?
I have http://godrb.com/ monitoring that resque stays running, so it could be related to that.
I'm on a Windows 7 VM with Apache. I'm trying to get Bind DNS setup to route subdomains to the same place as the main domain. The main domain routes correctly to 172.16.5.1 as specified in the hosts file. But the subdomains are still routing to the 127.0.0.1
I haven't added anything to the httpd.conf because I don't *think I need to. Here are my bind files. Any ideas of what might be wrong? I'm also not sure what 'hostmaster' should be changed to, if anything, in the zone file.
/etc/named file:
options {
directory "c:\named\zones";
allow-transfer { none; };
recursion no;
};
zone "." IN {
type master;
file "db.eg.com.txt";
};
#allow-transfer { none; };
# Use with the following in named.conf, adjusting the allow list as needed:
key "rndc-key" {
algorithm hmac-md5;
secret "Rha8Z8AKxOeg+asqZQ==";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
zones/db.eg.com.txt file:
$TTL 6h
@ IN SOA eg.com. hostmaster.eg.com. (
2011100911
10800
3600
604800
86400 )
@ NS eg.com.
* IN A 172.16.5.1