Storeman constantly network error

I have updated to 5.0.0.72 but I haven’t opened storeman for sometime so I am not sure if it is related.

From yesterday till now, whenever I open storeman, it won’t load anything and gives “network error” at top. I can open openrepos.net fine from browser.

I am using an Xperia 10 V, rebooted several times.

1 Like

Turns out it is because I am connecting to mullvad VPN. Why is mullvad VPN IP suddenly starts getting blocked…

(the reason I didn’t find this immediately is that the button of VPN in drop down menu seems to not work, when I click it there it will attempt to disconnect VPN but immediately reconnects

1 Like

Can you mark your answer as solution ?

I have had the same thing for a while now. So it’s not related to your update.
But I wonder why that happens…
Does Storeman block VPNs? And if so, why?

The Storeman app does no such thing.

But it relies on

  1. the local ssu/zypp repo configuration
  2. nework access to the openrepos website.

Now there are several things that can go wrong here (all out of scope for the Storeman app):

  • Local repo config may be wonky. E.g. a repo is configured which does not exist, or specified wrongly in some other way.
    This can break repo refresh.

  • It may also be affected by some overzealous ‘privacy/blocking’ configuration. Jolla uses cloudfront.net for their repos.
    Even though those are not related to Storeman/Openrepos, blocking cloudfront breaks the repo refresh.

  • Access to the OpenRepos website is somehow not working. This has been frequently the case with their TLS certificates being wrong, but may have other reasons.
    OR is hosted at Hetzner in Germany. They might have something in place that prevents access via e.g. Mullvad VPN.

There is some wisdom that has been true since the dawn of Jolla:

pkcon refresh fixes everything.

Well not really, but issuing the command may give some hint what’s not working.

4 Likes

As a long time Linux-user, I should have come up with this myself :man_facepalming:

Thanks anyways

It gives the following output:

Schwerwiegender Fehler: Fehler beim Download (curl) für 'https://sailfish.openrepos.net/Mister_Magister/personal/main/repodata/repomd.xml':
Fehlercode: 'Connection failed'
Fehlermeldung: 'Could not resolve host: sailfish.openrepos.net'

It does this for basically every user (not just the Mister_Magister here).
When I disable my VPN connection, everything works fine, so it’s probably either privacy blocking on the VPN side or OpenRepos/Hetzner blocking VPN access.

But I suspect the latter, since I have been using this VPN-config for over a year and it just stopped working this year (a few months ago but I don’t remember exactly when this started)

Storeman does not block anything. It as a DNS server that you are using is blocking and not resolving openrepos.net domain.

edit: fixed domain name

Same here and so I just uninstalled it and right away installed it and it works again :wink:.

No, I don’t think so. When I use a VPN, my VPN provider has the DNS server, right?

So I tested it on my PC and disabled all DNS blocking capabilities of the VPN client (Advertising, Tracker, Malware, Gambling, Adult Content and Social Media). Originally, I had all of them turned on and then turned them off one by one and tested the connection with the ping command, until everything was disabled.

Every try, pinging storeman.net didn’t work, giving either ping: storeman.net: System error or ping: ``storeman.net``: Name or service not known

But when I disconnect from VPN, I can ping it just fine.

And I doubt that the default configuration of the VPN blocks some links (wouldn’t really make sense, would it?)

What did you reinstall? Storeman? Or a VPN?

The correct domain address is openrepos.net. I was writing too fast. You can think whatever you want but the

error means that the problem is with DNS resolving.

Ah, that makes more sense. Unfortunately still the same issue.

I would be interseted to know what you think. Do you think it’s possible that the VPN provider blocks openrepos.net without me specifying any blocking?

If you are not familiar with tools like dig you can easily test it using Firefox with "DNS over HTTPS " set in settings. There are two default servers and both should works.
For me it looks like you are using too much blocking apps :slight_smile: and one of them “works” to well.

I did uninstall and reinstall Storeman. Then Storeman worked again.

1 Like

Okay so I tested this and indeed it works with DNS over HTTPS while still having VPN active.

The thing is: I don’t have any blocking apps installed as far as I’m aware of. I have only some DNS blocking activated for my VPN but as I posted earlier, even with those disabled it doesn’t work.

This unfortunately didn’t work for me

Try to switch all of them off at once. A blocked domain can be in two or more categories.

I already tried - didn’t work.

I see that any of Mulvad DNS servers is not resolving openrepos.net. You can try to change DNS from 194.242.2.2 for 1.1.1.1 ( or other public DNS ) in settings. Sometimes disabling IPv6 helps as well in such cases.

1 Like

However, on my case,

when I have VPN on. I configured globally to use mullvad dns only (through router. It is possible that something is actually bypassing it.)