No longer loading images on Firefox 85.0

[werewolfgold]

I'd been using the extension until last week when suddenly the images stopped loading. I tried restarting my app, deleting and reinstalling the add-on, deleting my cache, etc. But, nothing's happening.

The add-on says that some images here and there are being processed (but definitely not all), and I can see it making connections and transferring from my Bandwidth Hero at the bottom of the screen, but no images are are loading. And trying to create a new node using the template is only giving me an error. Everything was fine until last week.

Has anyone else had problems?

[werewolfgold]

It is definitely Firefox 85.0. Rolling back to 84.02 allows the extension to work correctly and everything works fine in Google Chrome. I have no idea what changed in 85.0 but someone with more technical know-how than I should investigate.

It may have something to do with their changing network protections.
https://blog.mozilla.org/security/2021/01/26/supercookie-protections/

[NetuxDevelopment]

With Firefox 86.0 the same thing happens and looking at the error in the console it tells me that: "401 Unauthorized"
Anyone know how to fix it?

[arun54321]

Working fine on firefox 89

[werewolfgold]

Weird. It's still a no-go for me.

[arun54321]

Working fine on Firefox 90. I think your proxy server is not working. Have you set-up your own compression service at first place? Just installing the extension isn't enough for get it working.

[werewolfgold]

The entire premise of the thread is that it used to work and then it stopped working. And my second post stated that it started working again once I rolled back Firefox to 84.02, and that it works fine in Google Chrome, which it still does. So yes, I set up the compression service.

I'll can try to check if another extension is getting in the way somehow.

[NetuxDevelopment]

Como lo tienes configurado? El mié., 14 de julio de 2021 10:38 p. m., Arun ***@***.***> escribió:

…

Working fine on Firefox 90. I think your proxy server is not working. Have you set-up your own compression service at first place? Just installing the extension isn't enough for get it working. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP3JXZCM4S62ZG7ML7KUPBLTXZJ27ANCNFSM4W33IRJA> .

[NetuxDevelopment]

How do you have it configured? El mié., 14 de julio de 2021 10:38 p. m., Arun ***@***.***> escribió:

…

Working fine on Firefox 90. I think your proxy server is not working. Have you set-up your own compression service at first place? Just installing the extension isn't enough for get it working. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP3JXZCM4S62ZG7ML7KUPBLTXZJ27ANCNFSM4W33IRJA> .

[werewolfgold]

I, too, am getting the "401" console error. Here's what's going on in the error. The first thing that comes to mind is that it has something to do with HTTP vs. HTTPS. But it might be something else.

[HTTP/1.1 401 Unauthorized 740ms]
	
**GET** https://____________________.herokuapp.com/?url=https://avatars.githubusercontent.com/u/40169871?s=60&v=4&l=40
- Status: 401 Unauthorized
- Version: HTTP/1.1
- Transferred: 246 B (13 B size)
- Referrer Policy: no-referrer-when-downgrade

**Response Headers (233 B)**
- Connection: keep-alive
- Content-Length: 13
- Date: Thu, 15 Jul 2021 10:31:17 GMT
- Server: Cowboy
- Via: 1.1 vegur
- Www-Authenticate: Basic realm="Bandwidth-Hero Compression Service"
- X-Powered-By: Express

**Request Headers (497 B)**
- Accept: image/webp,*/*
- Accept-Encoding: gzip, deflate, br
- Accept-Language: en-US,en;q=0.5
- Connection: keep-alive
- DNT: 1
- Host: _____________________.herokuapp.com
- Referer: https://github.com/ayastreb/bandwidth-hero/issues/56
- Sec-Fetch-Dest: image
- Sec-Fetch-Mode: no-cors
- Sec-Fetch-Site: cross-site
- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0

[Chouffy]

I had this 401 issue and I had set up a username/password on my Heroku proxy.

When I pass the username & pass in Bandwidth Hero URL, it will work like a charm.
URL format is https://USERNAME:PASSWORD@host.heroku.com

Hope this helps!

[werewolfgold]

I had this 401 issue and I had set up a username/password on my Heroku proxy.

When I pass the username & pass in Bandwidth Hero URL, it will work like a charm.
URL format is https://USERNAME:PASSWORD@host.heroku.com

Hope this helps!

This worked. Thanks.

It's weird because it always gave me a prompt to enter in the username and password, and that worked fine until February. I don't know what changed.

[jacky780001]

I had this 401 issue and I had set up a username/password on my Heroku proxy.

When I pass the username & pass in Bandwidth Hero URL, it will work like a charm.
URL format is https://USERNAME:PASSWORD@host.heroku.com

Hope this helps!

Could you please be more specific where and how to implement this configuration. I've been facing the same issue since last 6 months

[werewolfgold]

I had this 401 issue and I had set up a username/password on my Heroku proxy.
When I pass the username & pass in Bandwidth Hero URL, it will work like a charm.
URL format is https://USERNAME:PASSWORD@host.heroku.com
Hope this helps!

Could you please be more specific where and how to implement this configuration. I've been facing the same issue since last 6 months

When you go into the Bandwidth Hero menu, click on "Compression Settings" and "Configure data compression service."
From there, in the "Data Compression Service" URL box, you're going to put:
https://___________________:_____________________@______________________.herokuapp.com/

In the first space, put your username. The second, put your password. The third, put the name of your compression service.

It'll look like this.
https://thisismyusername:thisismypassword@thisisthenameofmyservice.herokuapp.com/

[jacky780001]

I had this 401 issue and I had set up a username/password on my Heroku proxy.
When I pass the username & pass in Bandwidth Hero URL, it will work like a charm.
URL format is https://USERNAME:PASSWORD@host.heroku.com
Hope this helps!

Could you please be more specific where and how to implement this configuration. I've been facing the same issue since last 6 months

When you go into the Bandwidth Hero menu, click on "Compression Settings" and "Configure data compression service."
From there, in the "Data Compression Service" URL box, you're going to put:
https://___________________:_____________________@______________________.herokuapp.com/

In the first space, put your username. The second, put your password. The third, put the name of your compression service.

It'll look like this.
https://thisismyusername:thisismypassword@thisisthenameofmyservice.herokuapp.com/

Thanks, it worked!

[NetuxDevelopment]

works perfectly in the latest version of firefox with "URL format is ***@***.***"