Open fearful-symmetry opened 11 months ago
data-sync-user
commented
11 months ago ➤ Bianca Hidecuti commented:
Hello,
Not sure if this is the same issue or not, but this also happens on the 2.16 build, while on Linux, after a fresh install. More details here: https://mozilla-hub.atlassian.net/browse/VPN-5159 ( https://mozilla-hub.atlassian.net/browse/VPN-5159|smart-link )
data-sync-user
commented
11 months ago ➤ Santiago Andrigo commented:
We should check this in 2.16, and see if it gets resolved.
nickavem
commented
10 months ago I am messing around with creating a COPR, and getting the same issue. What is weird is that it always happens on the first boot, but if you log out and back in, it fixes itself.
fearful-symmetry
commented
10 months ago Think I might have figured it out; it's my PiHole. Had a suspicion, disabled the PiHole, and the home screen popped back up. The privacy settings on the PiHole means that I'm not logging DNS queries, but it looks like my blocklists are hitting the following domains:
Match found in https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts:
mozillaname.com
incoming.telemetry.mozilla.org
Match found in https://mkb2091.github.io/blockconvert/output/hosts.txt:
mozilla.com.112.2o7.net
mozilla-firefox-64-bit.apponic.com
mozilla-firefox-beta.apponic.com
mozilla-firefox-portable.apponic.com
mozilla-firefox.apponic.com
mozilla.org.domain.name
services.addons.mozilla.org.domain.name
aus5.mozilla.org.domain.name
mozillamaintenanceservice.duckdns.org
crash-stats.mozilla.com
data.mozilla.com
fhr.data.mozilla.com
input.mozilla.com
metrics.mozilla.com
telemetry-incoming.r53-2.services.mozilla.com
tracking.services.mozilla.com
snippets.mozilla.com
download-stats.mozilla.org
telemetry.mozilla.org
aggregates.telemetry.mozilla.org
analysis-output.telemetry.mozilla.org
dictionary.telemetry.mozilla.org
fxos.telemetry.mozilla.org
glam.telemetry.mozilla.org
grafana.telemetry.mozilla.org
gud.telemetry.mozilla.org
iodide.telemetry.mozilla.org
loop.telemetry.mozilla.org
missioncontrol.telemetry.mozilla.org
probeinfo.telemetry.mozilla.org
probes.telemetry.mozilla.org
public-data.telemetry.mozilla.org
reports.telemetry.mozilla.org
sql.telemetry.mozilla.org
workflow.telemetry.mozilla.org
live.mozillamessaging.com
support.live.mozillamessaging.com
mozillaname.com
supportmozilla.org
Match found in https://raw.githubusercontent.com/d43m0nhLInt3r/socialblocklists/master/Tracking/trackingblocklist.txt:
incoming.telemetry.mozilla.org
geo.mozilla.org
geo.mozilla.org
telemetry-experimentJust grepping through the source, I'm guessing that *.telemetry.mozilla.org might be involved.
At the risk of sounding like I'm wagging my finger after creating a problem of my own making, I would suggest a follow-up issue for "draw the UI even if a network connection fails" or just "print obvious error in case of network connection failure"
Describe the bug After some period of time (or perhaps restarts of the VPN/my laptop?), the home screen of the VPN UI appears blank:
Screenshot
All other tabs in the UI, such as messages and settings, work normally.
The bug can be (temporarily) fixed by rebuilding/reinstalling according to above wiki instructions, although it seems to appear again after a few days.
Full text of log:
VPN version: built according to Wiki instructions from commit 096eadaa46d8539fbdd8309e4e9951e792f61c41, release version in UI: 2.17.0 (2.202306241555)
Affected Platforms: Feoora 38,
6.3.11-200.fc38.x86_64Prerequisites: Issue appears consistently, although I'm not 100% what exactly triggers it.
Steps to reproduce: 1) Build & install on fedora according to instructions 2) Wait some period of time
Expected result: The home screen continues to work
Actual result: The home screen appears blank.
┆Issue is synchronized with this Jira Bug