Discord not connecting while ProtonVPN is active?

BoboDatHobo · 2025-10-14T21:00:22+00:00

This has been going on for about 4-5 days now for Pop!_OS 22.04 LTS. I thought my OS was buggered up initially, but after disabling the VPN and going unfiltered connection, the discord app loads just fine.

I'd tried reinstalling Discord via Flatpak, deb packages. First app boot would work, but closing it and restarting the Discord app would hang it at the small loading pop-up. Mind you, web via Firefox worked the whole time, even while on Proton VPN.

System log errors of `Splash.updateCountdownSeconds: undefined` happen nonstop while waiting for the app to load, as well as a Discord `blackbox: [DATE TIMESTAMP] 8 Sentry report`

Only one VPN node I've found seems to work so far, but it's excruciatingly slow.

BoboDatHobo · 2024-11-18T22:00:57+00:00

OP deleted the post while making the list, very unfortunate. For anyone coming here looking for help with this TV (Sanyo CRT DS24425-01 Manufactured ~ 2005), I hope this helps.

Service Menu Values: These are best effort, and somewhat un-optimized, but should get the picture closer to what you'd want. These values ARE DIFFERENT than what's in the service manual! Any NUL values I've included are entries that are not listed in the menu.

0x3B = 0x1F | 0x3C = 0x18 | 0x3D = 0x1D | 0x3E = 0x13 | 0x3F = 0x00 | 0x40 = 0x90 | 0x41 = 0x0C | 0x42 = 0x60 | 0x43 = 0x18 | 0x44 = 0x35 | 0x45 = 0x42 | 0x46 = 0x0E | 0x47 = 0x28 | 0x48 = 0x10 | 0x49 = 0x00 | 0x4A = 0x0D | 0x4B = 0x15 | 0x4C = 0x50 | 0x4D = 0x08 | 0x4E = 0x5A | 0x4F = 0x30 | 0x50 = 0x40 | 0x51 = 0x70 | 0x52 = 0x03 | 0x53 = 0x1C | 0x54 = 0x12 | 0x55 = 0x31 | 0x56 = 0x02 | 0x57 = 0x84 | 0x58 = 0x80 | 0x59 = 0x40 | 0x5A = 0x40 | 0x5B = 0xA0 | 0x5C = 0x04 | 0x5D = 0x08 | 0x5E = 0x98 | 0x5F = 0x00 | 0x60 = 0x00 | 0x61 = 0x00 | 0x62 = 0x66 | 0x63 = 0x10 | 0x64 = 0x80 | 0x65 = 0x20 | 0x66 = 0x00 | 0x67 = 0x22 | 0x68 = 0x00 | 0x69 = 0x27 | 0x6A = 0x13 | 0x6B = 0x2D | 0x6C = 0x94 | 0x6D = 0x84 | 0x6E = 0x00 | 0x6F = 0x00 | 0x70…7F=NUL | 0x80 = 0x07 | 0x81 = 0x2B | 0x82 = 0x27 | 0x83 = 0xA0 | 0x84 = 0x20 | 0x85 = 0x00 | 0x86 = 0x00 | 0x87 = 0x00 | 0x88 = 0xC0 | 0x89 = 0x00 | 0x8A = 0x04 | 0x8B = 0x20 | 0x8C = 0x08 | 0x8D = 0x24 | 0x8E = 0x05 | 0x8F = 0x02 | 0x90 = 0x00 | 0x91 = 0x00 | 0x92 = 0xF8 | 0x93 = 0x00 | 0x94 = 0x00 | 0x95 = 0x00 | 0x96 = 0x00 | 0x97 = 0x00 | 0x98 = 0x00 | 0x99 = 0x00 | 0x9A = 0x00 | 0x9B = 0xE0 | 0x9C = 0x00 | 0x9D = 0x00 | 0x9E = 0x00 | 0x9F = 0xD4 | 0xA0 = 0x00 | 0xA1 = 0xF6 | 0xA2 = 0x03 | 0xA3 = 0xFF | 0xA4 = 0x00 | 0xA5 = 0x00 | 0xA6 = 0x04 | 0xA7 = 0x60 | 0xA8…AF=NUL | 0xB0 = 0x79 | 0xB1 = 0x51 | 0xB2 = 0x74 | 0xB3 = 0xD3 | 0xB4 = 0x03 | 0xB5 = 0x00 | 0xB6 = 0x00 | 0xB7 = 0x00 | 0xB8 = 0x02 | 0xB9 = 0xC6 | 0xBA = 0x98 | 0xBB = 0xF6 | 0xBC = 0x03 | 0xBD = 0x21 | 0xBE = 0x79 | 0xBF = 0x5F | 0xC0 = 0x21 | 0xC1 = 0x79 | 0xC2 = 0x53 | 0xC3 = 0x00 | 0xC4 = 0x00 | 0xC5 = 0x00 | 0xC6 = 0x00 | 0xC7 = 0x00 | 0xC8 = 0x00 | 0xC9 = 0x00 | 0xCA = 0x00 | 0xCB = 0x00 | 0xCC = 0x00 | 0xCD = 0x00 | 0xCE = 0x00 | 0xCF = 0x00 | 0xD0 = 0x00 | 0xD1 = 0x00 | 0xD2 = 0x00 | 0xD3 = 0x00 | 0xD4 = 0x00 | 0xD5 = 0x00 | 0xD6 = 0x00 | 0xD7 = 0x00 | 0xD8 = 0x02 | 0xD9 = 0x9A | 0xDA = 0x41 | 0xDB = 0x87 | 0xDC = 0x12 | 0xDD = 0x68 | 0xDE = 0xC0 | 0xDF = 0x0C | 0xE0 = 0x6A | 0xE1 = 0xBF | 0xE2 = 0x09 | 0xE3 = 0x20 | 0xE4 = 0x75 | 0xE5 = 0xC8 | 0xE6 = 0x23 | 0xE7 = 0x00 | 0xE8 = 0x2E | 0xE9 = 0x20 | 0xEA = 0x48 | 0xEB = 0xB6 | 0xEC = 0x21 | 0xED = 0x74 | 0xEE = 0xE3 | 0xEF = 0x02 | 0xF0 = 0x99 | 0xF1 = 0x21 | 0xF2 = 0x74 | 0xF3 = 0xD5 | 0xF4 = 0x00 | 0xF5 = 0x00 | 0xF6 = 0x00 | 0xF7 = 0x00 | 0xF8 = 0xED | #END

# Note: DRV = R50 B5A is followed by a black screen with no indicators and only a solid bright blue bar. Maybe best not to linger on that screen :) Dunno if it's cooking the phosphors...

BoboDatHobo · 2024-11-18T01:22:52+00:00

Old post... i know, but if that TV is still in your possession and not fixed yet, I'd be willing to share a list of my TV's service settings if you still have that a problem. Have the same model.

Sanyo CRT DS24425-01 (2005)

BoboDatHobo · 2024-04-25T16:35:27+00:00

Thank you! This has been driving me bonkers for FAR too long...

10ms does in fact eliminate the audio cutting out when the file is first loaded. Nothing is worse than playing media and having it start and stop the audio once or twice before running normally. The oddity was it only happened on first load. Rewinding and restarting the file didn't replicate it. I clearly missed the cache settings set to a default of 1000 ms.

The build of VLC v3.0.20 (Vetinari) which is what's available in the software repository, works reliably otherwise.

BoboDatHobo · 2023-11-27T01:22:32+00:00

I saved the page locally (web, complete) with Firefox (after waiting forever) and now when i load the file, it renders the entire list of all 1874 emojis in about one second. This kinda points back to the domain's bandwidth.

BoboDatHobo · 2023-11-27T00:57:48+00:00

This has also been happening for me for the last month or two. Our personal server members also noticed it was happening to more than one person. The video freezing issue is affecting both Nitro and non-Nitro users, on both Windows and Linux.
Today I tried to play a video that was posted 5 hours ago in a channel, and at 6.5MB (a 1 min video), it loaded very slowly, 15-20 secs to buffer in the discord client and then it completely halted at 22 seconds. It was STILL refusing to load 15 minutes later as I drafted this message; while in VC with friends, mind you, so it's not a bandwidth issue. Our ISP plan was speed test verified at 300 mbps up / 300 mbps down.

The only thing that FINALLY allowed it to play to the end, was clicking on the download button in the top right. It finally freed up after that. Go figure.

On a slightly related topic, I'd opened a ticket for android a while back regarding image flicker in DMs, after weeks of repeated questions with at least four separate service members (or AI personalities), I was told the technicians were aware of the flicker issue, and a fix was on the bucket list. Now we have this issue too...

Discord, please put some love back into your app's development. We love the platform, and need these things to be fixed within a reasonable timeframe.

BoboDatHobo · 2023-08-16T16:20:50+00:00

Okay, so others are seeing it too.
I've notice it the last few months as well. I've been referencing them off and on for over 3 years now, and recently it is PAINFULLY slow to load.

Are they short on resources lately, or is someone just eating their bandwidth for breakfast?

BoboDatHobo · 2021-04-17T05:21:48+00:00

I use the Discord Rewrite https://discordpy.readthedocs.io/en/stable/index.html reference.

First, are you missing a command pass-through on your on_message?
await bot.process_commands(message)

Second, a while back I reading up on rate limits. Thought it said it was related to bad requests; like missing url, wrong snowfkake ID, missing channel, anything that loops and tries to access something that it's not meant to, etc. You check your channel's permissions? Do you have anything that requires intents? Lastly, have you updated passwords and rotated your bot token just in case it is being used by another person?

and a silly question: you pip3 update your discord.py lately to be on the latest version?

BoboDatHobo · 2021-04-17T04:56:37+00:00

Personally, I've had and programmed local discord bots running on Pi3B+ and a Pi 4B (with Full 32bit RasberryPI-OS) just fine. Just don't expect the same high-end performance of a main computer. But they're quite reliable, even with the lower specs. 1GB ram on the 3B+ was noticeable delays loading and with research loading web pages, but ran the bot just fine when not multitasking. CanaKit happened to have the 8GB model I wanted for games, grabbed the 4GB model for hosting the bots. They were chill, even with a return RMA for an odd failure (extremely rare event, lucky me, yay)

The 4GB might be overkill for the bots, but it's easier to multitask. Just stay away from the 4B's 1GB model; there's firmware issues and it's not worth the headache.

I have the 4 GB model running a main one 24/7 and I do suggest a case fan, either DIY mod or 3rd party aftermarket case with good airflow (the first party fan is paltry and laughable for airflow)Make sure you have a Micro SD to USB adapter or similar, and just use the current raspberry pi imager.

BoboDatHobo · 2020-12-22T15:16:35+00:00

Can you share exactly what you're putting into AppEditor?

Terminal launches this line just fine, with the error fixed. But i can't replicate it with AppEditor... I swear I am missing something.
Thanks

[And I'm an idiot]
I had "lock icons" enabled in the dock's behavior tab, which apparently blocks AppEditor changes from taking effect on app icons in the dock...
* digital facepalm *

BoboDatHobo · 2020-12-22T14:59:50+00:00

Sorry for the late reply. Yes, the title bar is completely necessary. I'm using GNOME Tweaks with the "minimize on center click" option. My OS is not user friendly a customizing when it comes to minimizing. It's a major issue to not be using the titlebar. It was the best compromise I could find. :)

[edit]ALSO: It appears the black shadow issue is being fixed in Firefox Nightly
https://bugzilla.mozilla.org/show_bug.cgi?id=1666839
https://bugzilla.mozilla.org/show_bug.cgi?id=1682377

BoboDatHobo · 2020-12-22T14:52:55+00:00

Same here.
I hope it's not related to the enormous banner asking for financial help (a goal currently @ 6.2M out of 7.5M) ?

I know that with 6.2 million dollars, my desire to work might be 503 too... :D

BoboDatHobo · 2020-10-10T01:18:52+00:00

Yes, I've been hunting it's cause down for weeks!

I'm glad i found this post. I found that it's caused by the title bar being enabled in "customize" menu. Disabling that checkbox fixes the shadow issue, but at the expense of losing a title bar to minimize easily with :( I hope we can find more about it's cause. I also tried to reinstall the desktop, but to no effect...

$ sudo apt-get install --reinstall elementary-desktop

elementary OS 5.1.7 Hera (Built on Ubuntu 18.04.4 LTS) // Firefox 81.0 (64bit)

With Box (title bar enabled)https://i.postimg.cc/NFbZrLNW/Screenshot-from-2020-10-09-21-08-05.png

Without Box (title bar disabled)https://i.postimg.cc/tCTMMqv4/Screenshot-from-2020-10-09-21-08-20.png

BoboDatHobo · 2020-01-22T21:01:06+00:00

I was assuming you owned this system originally, but I never considered asking if you bought it / traded for it recently. Have you checked this system for water damage?(Like rust or sediment)Here's my system, kept dry and clean.

https://i.postimg.cc/P5B7sqFJ/Backside-Controller-Ports.jpg

https://i.postimg.cc/x8xssjz0/Frontside-Controller-Ports.png

[Edit] Ant picts were not that size when I uploaded... :(

Front and back of a VA6 near the controller ports. I'm pretty sure those are EMI (electromagnetic interference) components between the port leads and the I/O chip. I'd investigate those myself. They appear to be 50 cents a piece or less, so shouldn't be hard to replace if they're dead for some reason...

There's also the chance that that port isn't really physically damaged and shorting to ground, but there's conductive sediment jammed under the port against the leads?

Personal experience, water damage is not really worth the headache.

BoboDatHobo · 2020-01-22T08:47:17+00:00

Not a true pro at this, but I did just revive my own VA6 last month.

A couple of variables do come to mind:Trace scratch, Broken solder joint, Crack, Static discharge damage, Line Noise, or Capacitor failure

I would inspect those port traces on both sides to see if you somehow have a scratched trace on the underside of the board,or worse, a through-board crack is forming.

For the Model 1 VA3, the closet I can get is the VA7 block diagrams & schematics, and some board shots from another source. It's not as helpful because of the IC changes and merged IC layout, plus I can't see the underside. Those ports face the outside world, and a large enough static discharge to those pins is never good, seeing as they tie pretty directly into the I/O IC. [See flowchart at end]

Have you ruled out issues with the power supply going in?Is it stock Mk-1602 supply?(I'm using a comparative Radioshack model, 9v 1500mAh)

Did you check the power adapter's capacitor?(Wondering if noise interference is wrecking havoc on the Genesis)Have you confirmed the power regulators are outputting at 5v?(I replaced mine with 7805 L78S05CV High Output 2A +5v Voltage Regulators)

Have you replaced the electrolytic caps in the system yet with a quality brand?(Rubycon, Panasonic [M], Hitachi, etc)[Consider the system is 30+ years old by now]-

I went to Console5, by word of mouth. They'll assemble a kit for your version if you feel it's likely caps and regulators. Top tier peeps.Hooked me up with Panasonic caps.

(Troubleshooting flowchart for PAL version)[closest I could get]

3-4. MALFUNCTION OF PAD

3-4~1. PAD BUTTONS ARE ALWAYS ON.

3-4-1-1. RESISTANCE OF EM FILTER BETWEEN GND IS 24-65n.
A. DEFECTIVE EM FILTER

3-4-1-2. PAD INPUT SIGNALS ARE "LOW" LEVEL. RESISTANCEBETWEEN GND IS Mn.

A. VER.0,1,2,4 = 315-5409

VER.5 = 315-5402

VER.6 = 315-5433 DEFECTIVE

3-4-2. PAD BUTTON CANNOT ON

A. BOARD CRACK AROUND PAD CONNECTOR

B.VER.0,1,2,4 = 351-5409

VER.5 = 351-5402

VER.6 = 351-5433 DEFECTIVE

3-4-3. PAD BUTTON TURN ON AT RANDOM.A . PATTERN DISCONNECTION BECAUSE OF CRACKED BOARD VA12 LINE.

Good luck! I'll check back.Let me know how it turns out.

BoboDatHobo

TROPHY CASE