tickets #71131
closed
twsnapshot.o.o is down / not reachable
Added by cboltz over 3 years ago.
Updated over 3 years ago.
Category:
Servers hosted in Provo
Description
twsnapshot.o.o is down, or at least not reachable from the outside. I verified this a) from my own laptop and b) got it verified by letsencrypt, which failed on certificate renewal (see #71104)
curl -v twsnapshot.opensuse.org directly started on provo-mirror works, and twsnapshot.o.o has a separate IP, therefore I wonder if this could be a firewall issue.
FYI: I had to remove two domains from dehydrated to fix certificate renewal:
- twsnapshot.o.o doesn't respond at all (= this ticket)
- debuginfod.o.o is served via proxy-prv (and therefore proxy-prv needs to handle the certificate) - unrelated to this ticket ;-)
- Private changed from Yes to No
- Status changed from New to Feedback
- Assignee changed from lrupp to cboltz
Just followed the debugging path for reference...
from /etc/nginx/vhosts.d/001-tumbleweed-snapshots.conf on provo-mirror.o.o:
listen 91.193.113.73:80
nginx is up and running, bond to the port in the config ('ss -tulpen | grep 91.193.113.73')
input_ext iptables chain shows:
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
curl -H "Host: tumbleweed.opensuse.org" http://91.193.113.73
from another machine does indeed not work. I will open a ticket with SUSE-IT to see if they changed some firewall settings.
Question: where (which machine) did you adjust dehydrated?
- Assignee changed from cboltz to lrupp
lrupp wrote:
curl -H "Host: tumbleweed.opensuse.org" http://91.193.113.73
from another machine does indeed not work. I will open a ticket with SUSE-IT to see if they changed some firewall settings.
Thanks!
Question: where (which machine) did you adjust dehydrated?
On provo-mirror, see my comment in ticket #71104 for details.
- Status changed from Feedback to New
- Status changed from New to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF