Page MenuHomeWolfplex

No A record on wolfplex.be
Closed, ResolvedPublic

Description

w3m http://wolfplex.be doesn't work.

Thank you to @amj to have noticed that.

Event Timeline

dereckson raised the priority of this task from to Needs Triage.
dereckson updated the task description. (Show Details)
dereckson added a project: IT.
dereckson added subscribers: dereckson, amj.
dereckson claimed this task.
dereckson triaged this task as Unbreak Now! priority.

Strange, vhost added, seems okay for w3m, but not for Chrome.

I suspect w3m redirects to www?

By telnet, it works too.

$ telnet ysul.nasqueron.org 80
Trying 212.83.187.132...
Connected to ysul.nasqueron.org.
Escape character is '^]'.
GET / HTTP/1.1
Host: wolfplex.be

HTTP/1.1 302 Moved Temporarily
Server: nginx/1.8.0
Date: Tue, 05 Jan 2016 23:33:38 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/5.6.16
Location: https://www.wolfplex.be/2015/
dereckson closed this task as Resolved.EditedJan 16 2016, 7:38 PM

upstream has fixed the issue, ensuring nginx listens each vhost in IPv6.

Reference: http://devcentral.nasqueron.org/T672