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

yum.qubes-os.org is down #3811

Closed
edwintorok opened this Issue Apr 10, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@edwintorok

edwintorok commented Apr 10, 2018

Qubes OS version:

Qubes release 4.0 (R4.0)

Affected component(s):

qubes-dom0-update


Steps to reproduce the behavior:

sudo qubes-dom0-update

Expected behavior:

Able to reach repository

Actual behavior:

Failed to synchronize cache for repo 'qubes-dom0-current', disabling.
Failed to synchronize cache for repo 'qubes-templates-itl', disabling.

General notes:

Tried from a few different places, server is reachable but refuses connections:

wget http://yum.qubes-os.org
--2018-04-10 23:47:46--  http://yum.qubes-os.org/
Resolving yum.qubes-os.org (yum.qubes-os.org)... 82.94.215.165
Connecting to yum.qubes-os.org (yum.qubes-os.org)|82.94.215.165|:80... failed: Connection refused.

Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 11, 2018

Member

I can't reproduce this. The server is currently reachable over Tor. It appears that this was either a temporary issue that has since resolved itself or perhaps a problem on your end.

Closing this for now as "cannot reproduce." If you believe this is a mistake, or if anyone can reproduce the issue, please leave a comment, and we'll be happy to reopen this. Thank you.

Member

andrewdavidwong commented Apr 11, 2018

I can't reproduce this. The server is currently reachable over Tor. It appears that this was either a temporary issue that has since resolved itself or perhaps a problem on your end.

Closing this for now as "cannot reproduce." If you believe this is a mistake, or if anyone can reproduce the issue, please leave a comment, and we'll be happy to reopen this. Thank you.

@woju

This comment has been minimized.

Show comment
Hide comment
@woju

woju Apr 11, 2018

Member

Yes, this was a real failure related to an update, which went bad. Should be working now.

Member

woju commented Apr 11, 2018

Yes, this was a real failure related to an update, which went bad. Should be working now.

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Apr 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment