Fanbox posts no longer render

[Mæstro]

Beginning today, Fanbox posts (here an example) have failed to render in my browser. This occurs even in safe mode for me, but does not occur in a fresh profile. In addition to safe mode (to test whether an extension is to blame), I have tried switching to a Japanese VPN location, clearing my cookies and the cache, but any post I load appears as in the screenshot attached. The site’s homepage and artist pages render correctly despite this glitch. To make matters more bizarre, the test post appeared to load normally today on one attempt after this glitch emerged, using all my ordinary browser and other settings, before failing to load again. Part of me suspects this is just some bizarre disturbance in the ether that should go away by tomorrow, but are there further diagnoses or remedies I could try?

※As of 13.58 CEST, I had another single successful page load (for one of the artists I support, inaccessible to the public), followed by failure again. The fact that the problem occurs most, but not all times without anything changing on my (the client’s) end is the most bizarre facet of this to me.

[Moonchild]

Seems to work fine for me?

[Night Wing]

@ Mæstro

Since you say everything on Fanbox works with a clean fresh profile, but does not work with your old profile, then a logical conclusion would seem to point to something in your old profile is corrupted.

Profiles do get corrupted over time for whatever reason. Speaking just for myself; I make a clean new profile in Pale Moon, Waterfox and Firefox every six months for all three linux distros I use which are Mint, MX Linux and Debian.

If your problem continues with Fanbox for the next few days with your old profile; but not with the new profile, if the problem is not on Fanbox's end, then you just might have to use the new profile.

[Mæstro]

It might be worth noting that, whenever I try to load a Fanbox post and this problem occurs, its tab appears with its specific, Japanese name at first, but switches to ‘pixivFANBOX’ at the end. If I should transfer into a new profile, how do I preserve my extensions, special configuration features and other necessary adjustments I have needed make over the years?

[Gemmaugr]

After allowing Cloudflare, it gives a blank page, but also allowing pixiv and iframe after that, it shows the Japanese tab title and then the English one, and renders fine. Refreshed 3 times and still works.

[Mæstro]

After allowing Cloudflare, it gives a blank page, but also allowing pixiv and iframe after that, it shows the Japanese tab title and then the English one, and renders fine. Refreshed 3 times and still works.

Whether I permit requests to Iframe or not seems indifferent. As I observe further, I can see that the page loads first the Japanese, then the English and then, if it works as it ought, returns to the Japanese version. My best guess for what is happening is that the request has timed out more often than usual today. This would explain the sudden onset despite nothing in my browser changing and its erratic occurrence. There is also psychical evidence.

[Night Wing]

IIf I should transfer into a new profile, how do I preserve my extensions, special configuration features and other necessary adjustments I have needed make over the years?

You might want to take a look at Gemmaugr's post below your last post. It might solve your problem.

As for preserving all that you have made in your profile over the years, this is why many people do not want to make a new profile. For them, it is a "hassle". So they will take "many hours or days" trying to find what is in their old profile that is causing the problem.

Also, when you make a new profile, you have to check "each" item when your transfer info over from the old profile to the new profile, to find the problem. But if you want to hurry and take the easy way out and not check each item, you might inadvertently transfer what is causing the problem in the old profile to the new profile and the problem will most likely re-appear in the new profile.

I never use extremely old profiles. As I have said previously, I do not wait for problems to occur in a browser profile. This is why I make a new profile in all of my three browsers every six months. It takes me (now) about 30 minutes to configure a browser (bookmarks, settings, custom settings, etc) when I make a new profile.

For three browsers, the total is 90 minutes of time. But you have to keep in mind, I am not having any problems which I have to find and fix when I make a new profile. For me, my method is "preventive maintenance".

[Mæstro]

You might want to take a look at Gemmaugr's post below your last post. It might solve your problem.

I agree; he had given helpful information. At the time I am writing this, Fanbox posts appear to load more consistently, like normal. It is too early to tell whether this really has been a fluke that has since past, but I feel optimistic when writing this.

As for preserving all that you have made in your profile over the years, this is why many people do not want to make a new profile. For them, it is a "hassle". So they will take "many hours or days" trying to find what is in their old profile that is causing the problem.

Indeed, it is possible that, for my purposes and out of the need to ration my own effort, I would simply decide that Fanbox no longer works in Pale Moon for me and resort to checking it in Epiphany or Basilisk, like I did when Cloudflare broke the site in Pale Moon not long ago.

[Night Wing]

Off-topic:
@ Mæstro

For information purposes.

When I make a new profile and the old profile is not having a problem, what is in the old profile goes into the new profile. This is what I do every six months. But lets say I find a problem two months into the new profile.

I keep track of what I create or add during every six months. This way, if my problem came about during the previous two months into the new profile, I would then make a new profile and specifically start checking what I had added or changed during the last two months of time.

So if a problem is found, I have a relatively easy way, time wise, to find the problem and fix it.

I have seen some people go "years" without making a new browser profile. When they have a big problem, they will take not days, but "a week or weeks" trying to find the problem and fixing it.

[Mæstro]

When I make a new profile and the old profile is not having a problem, what is in the old profile goes into the new profile. This is what I do every six months. But lets say I find a problem two months into the new profile.

I keep track of what I create or add during every six months. This way, if my problem came about during the previous two months into the new profile, I would then make a new profile and specifically start checking what I had added or changed during the last two months of time.

Off-topic:
I have got a backup of my profile from end-January saved on a flash drive which I could use for this. (I copy my whole home directory irregularly, but never more than half a year apart.) Notable browser changes since the winter for me have been swapping DeCDN for Decentraleyes, installing Greasemonkey to block Invidious product placement, small additions to FoxReplace and other filters and two new passwords, one for a site I think this community would like. Restoring the old profile and making such manual changes as needed, including exporting and re-importing cookies if needed, would be far easier than beginning from scratch.

[Gemmaugr]

Off-topic:

For information purposes.

When I make a new profile and the old profile is not having a problem, what is in the old profile goes into the new profile. This is what I do every six months. But lets say I find a problem two months into the new profile.

I keep track of what I create or add during every six months. This way, if my problem came about during the previous two months into the new profile, I would then make a new profile and specifically start checking what I had added or changed during the last two months of time.

So if a problem is found, I have a relatively easy way, time wise, to find the problem and fix it.

I have seen some people go "years" without making a new browser profile. When they have a big problem, they will take not days, but "a week or weeks" trying to find the problem and fixing it.

I have to admit that I'm one of those that have used to the same profile for years.. Figuring out the problem is always a good learning experience though.

[Mæstro]

After a phase this evening where Fanbox was working as it ought again, it relapsed, although Iframe remained enabled. The seeming randomness by which the problem comes and goes, as mentioned, suggested a networking problem, perhaps to do with my building. (It is a block of flats which offers internet, so I have no administrative access to the network, but other tenants report from time to time its instability.) I want to think this problem will magically vanish just as it came without any action needed. In any case, only now have I read the suggestion to check the console, which has provided vital evidence to the problem’s nature. When I do this, it returns the following when I try to load the site in my ordinary profile. Mind that em dashes replace numerical values I suspect are linked to my account, and my system language is German:

Code: Select all

GET 
XHR 
https://api.fanbox.cc/post.info [HTTP/2.0 403 Forbidden 164ms]
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf https://api.fanbox.cc/post.info?postId=9869785. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt).  
(unbekannt)
Error: Network Error  
commons.—.js:—:—
Content Security Policy: Ignoriere “'unsafe-inline'” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “https:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “http:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “data:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert

In the fresh profile, it returns instead the following:

Code: Select all

◤◢◤◢◤◢◤◢ WARNING!! ◤◢◤◢◤◢◤◢
This is a browser tool for developers. Sharing any of the information listed here to any third party could lead to the unauthorized use of your personal information or registered payment information, and could put your account at risk.
◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢  
fanbox.—.js:—:—
Content Security Policy: Ignoriere “'unsafe-inline'” innerhalb von script-src: ‘strict-dynamic’ spezifiziert  
(unbekannt)
Content Security Policy: Ignoriere “https:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert  
(unbekannt)
Content Security Policy: Ignoriere “http:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert  
(unbekannt)

It would appear that Fanbox’s server is now forbidding me, ie returning a 403 error, for a necessary file specifying cross-site request permissions, when I try to access it; the problem goes away whenever it fancies to permit me. How can I alleviate this?

※When running in my regular profile on an occasion when Fanbox loads properly, the console log is as follows, confirming the 403 error is indeed to blame. Curiously, some of the excised numbers appear the same (by memory; I cannot be sure of this) in the below as in the fresh profile, but not the same profile when failing.

Code: Select all

◤◢◤◢◤◢◤◢ WARNING!! ◤◢◤◢◤◢◤◢
これは開発者向けのブラウザツールです。ここに記載されている情報を第三者に提供することは、個人情報や登録してる支払い情報の不正利用にも繋がり、あなたのアカウントを危険に晒す行為となります。
◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢  
fanbox.—.js:—:—
Content Security Policy: Ignoriere “'unsafe-inline'” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “https:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “http:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)
Content Security Policy: Ignoriere “data:” innerhalb von script-src: ‘strict-dynamic’ spezifiziert 
(unbekannt)

[Mæstro]

I have had a week to monitor Fanbox’s behaviour. Pages usually load, although it has sometimes required a few refreshes or trying again later. It might be worth noting that DuckDuckGo has tended, since shortly before this problem began, to demand I complete captchas in any browser I use. The situation is mild enough that I have no need to create a new profile. Incidentally, I discovered while checking my configuration settings that I had Fanbox’s user agent set to Firefox 38; deleting this seems not to have changed anything. I see this matter as closed.