For support with specific websites
Moderator: trava90
Forum rules
Please
always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
- Clear any current output
- Navigate or refresh the page in question
- Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
-
gospelmidi
- Moongazer

- Posts: 12
- Joined: 2025-05-13, 07:05
Post
by gospelmidi » 2025-05-13, 07:45
https://help.instagram.com/1009785806132609
Which web browsers work best with Instagram
To make sure you have best experience possible, we recommend using the most up-to-date version of one of the following browsers:
Google Chrome
Mozilla Firefox
Safari
Microsoft Edge
Apparently, Instagram disables their more sophisticated tools with "not recommended" browsers.
My about:config reports:
general.useragent.override.instagram.com default string
Mozilla/5.0 (%OS_SLICE% rv:68.0) Gecko/20100101 Firefox/68.0
Moonchild, please do not curse me. This is my first post.
Thank you for this wonderful, marvelous web browser.
Sincerely in Christ,
gospelmidi
-
andyprough
- Board Warrior

- Posts: 1183
- Joined: 2020-05-31, 04:33
Post
by andyprough » 2025-05-29, 20:59
gospelmidi wrote: ↑2025-05-13, 07:45
My about:config reports:
general.useragent.override.instagram.com default string
Mozilla/5.0 (%OS_SLICE% rv:68.0) Gecko/20100101 Firefox/68.0
Firefox 68.0 is ancient, many years old, I'm sure Instagram wants nothing to do with it. Can you change your string to use the latest Firefox ESR version 128.0 in those two spots where it's currently using 68.0? Maybe that would help you a little bit.
Also, you can use the Pale Moon add-on Sasuga to change user agents on a per-site basis:
https://addons.palemoon.org/addon/sasuga/
-
Moonchild
- Pale Moon guru

- Posts: 38404
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Post
by Moonchild » 2025-05-29, 21:10
The instagram override is a default-supplied one that was needed in the past to make it work. If it no longer works then it needs to be updated (but I don't know to what...)
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
Lexx Diamond
- Moon lover

- Posts: 88
- Joined: 2017-02-16, 18:26
- Location: Third Stone from The Sun
Post
by Lexx Diamond » 2025-07-14, 04:55
I have been having a problem with Instagram loading for the past few days. Despite clearing all the IG cookies from Palemoon. Every time I click on the option to log in I get an error message. Albeit IG works fine in my other 10 browsers. Here are some screen shots of what I am contending with. Click for lager image.
Any information leading to the resolution of this issue would be greatly appreciated. I was previously using version 32.4.1 with no such issue. I don't want to go back to the older version.
-
adoxa
- Astronaut

- Posts: 521
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2025-07-14, 07:00
PM doesn't like the selector - here's a
Modify HTTP Response filter to work around it.
Code: Select all
[["static.cdninstagram.com",["/^\\/rsrc.*\\.js$/",["matches(\"*:","matches(\""]]]]
-
adoxa
- Astronaut

- Posts: 521
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2025-07-14, 07:22
Moonchild wrote: ↑2025-05-29, 21:10
The instagram override is a default-supplied one that was needed in the past to make it work. If it no longer works then it needs to be updated (but I don't know to what...)
It's looking for Firefox 115, so the override could probably be removed.
-
Moonchild
- Pale Moon guru

- Posts: 38404
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Post
by Moonchild » 2025-07-14, 12:25
I'll remove it.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
Moonchild
- Pale Moon guru

- Posts: 38404
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Post
by Moonchild » 2025-07-27, 09:21
'*:-webkit-autofill' is not a valid selector [Caught in: caught error in module a [from CometPlaceholder.react] (base)]
they are now literally looking for blink or webkit. Nothing else. so even our addition of :autofill won't help because they want the -webkit- vendor prefixed one explicitly, or fail.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
FranklinDM
- Add-ons Team

- Posts: 631
- Joined: 2017-01-14, 02:40
- Location: Philippines
Post
by FranklinDM » 2025-07-27, 09:40
Moonchild wrote: ↑2025-07-27, 09:21
they are now literally looking for blink or webkit.
Perhaps we could also include this in the pseudo-classes covered by
layout.css.prefixes.webkit.
-
Moonchild
- Pale Moon guru

- Posts: 38404
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Post
by Moonchild » 2025-07-27, 11:05
Certainly an idea.
...That does make me wonder though about our new implementation of @supports selector() where the prefixed versions are specifically excluded. Should we not advertise that we support the prefixed ones as well, then? I can see the check going wrong if they use selector() to check it instead of just trying to use it.
"There is no point in arguing with an idiot, because then you're both idiots." - Anonymous
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
Lexx Diamond
- Moon lover

- Posts: 88
- Joined: 2017-02-16, 18:26
- Location: Third Stone from The Sun
Post
by Lexx Diamond » 2025-08-01, 18:05
Has anyone been able to find a viable fix to get Instagram to load? I'm using the latest version of PM.
-
Gemmaugr
- Lunatic

- Posts: 283
- Joined: 2025-02-03, 07:55
Post
by Gemmaugr » 2025-08-01, 18:43
Lexx Diamond wrote: ↑2025-08-01, 18:05
Has anyone been able to find a viable fix to get Instagram to load? I'm using the latest version of PM.
I only know how to view it (
https://imginn.com/), but not how to log in. I don't use it myself.
-
Lexx Diamond
- Moon lover

- Posts: 88
- Joined: 2017-02-16, 18:26
- Location: Third Stone from The Sun
Post
by Lexx Diamond » 2025-08-01, 18:59
Gemmaugr wrote: ↑2025-08-01, 18:43
Lexx Diamond wrote: ↑2025-08-01, 18:05
Has anyone been able to find a viable fix to get Instagram to load? I'm using the latest version of PM.
I only know how to view it (
https://imginn.com/), but not how to log in. I don't use it myself.
Thanks. I'm looking for a fix to be able to login to Instagram via PM.
-
Lexx Diamond
- Moon lover

- Posts: 88
- Joined: 2017-02-16, 18:26
- Location: Third Stone from The Sun
Post
by Lexx Diamond » 2025-08-05, 18:36
adoxa wrote: ↑2025-07-14, 07:00
PM doesn't like the selector - here's a
Modify HTTP Response filter to work around it.
Code: Select all
[["static.cdninstagram.com",["/^\\/rsrc.*\\.js$/",["matches(\"*:","matches(\""]]]]
This works like a charm. Thank you.