I'm getting this exact problem again today... if you want to check something.
Please post all forum bugs here
- Thread starter elgringo14
- Start date
-
Throughout the month of April 2024, participate in the FileJoker Thread Contest OPEN TO EVERYONE!
From 1st to 30th of April 2024, members can earn cash rewards by posting Filejoker-Exclusive threads in the Direct-Downloads subforums.
There are $1000 in prizes, and the top prize is $450!
For the full rules and how to enter, check out the thread -
Akiba-Online is sponsored by FileJoker.
FileJoker is a required filehost for all new posts and content replies in the Direct Downloads subforums.
Failure to include FileJoker links for Direct Download posts will result in deletion of your posts or worse.
For more information see this thread.
So, I'm having the CSS error, but I have a bit of javascript that you can put into a bookmarklet that I use to fix it:
Put that as a bookmark and it "fixes" the styles by properly loading in stylesheet (for me, and please let me know if it works for you).
You can paste it into your url bar to try it out, but it will remove the javascript: to prevent someone from being tricked into pasting malicious code. You'll have to type that bit in yourself.
With that in mind, here is the code spread out a bit so you can see it's innocuous.
So, the problem file is this (it returns with a 502 Bad Gateway error):
<link rel="stylesheet" href="/css/css=xenforo,form,public&style=8&dir=LTR&d=1595788270">
Through some messing around, I discovered the file would load if the last part of the query was removed: d=1595788270. If you just edit the url, the browser automagically downloads the file for you.
The code grabs all of the stylesheet links, find the right one (by checking if it includes xenforo) and lops off the last query variable.
I'm not sure what that query variable does, but the file loads properly without it for me.
Code:
javascript:(document.querySelectorAll('link[rel=stylesheet]').forEach(s => {if(s.href.includes('xenforo')) s.href = s.href.replace(/&d=\d*/,'');}))You can paste it into your url bar to try it out, but it will remove the javascript: to prevent someone from being tricked into pasting malicious code. You'll have to type that bit in yourself.
With that in mind, here is the code spread out a bit so you can see it's innocuous.
Code:
document.querySelectorAll('link[rel=stylesheet]').forEach(s => {
if(s.href.includes('xenforo'))
s.href = s.href.replace(/&d=\d*/,'');
}))<link rel="stylesheet" href="/css/css=xenforo,form,public&style=8&dir=LTR&d=1595788270">
Through some messing around, I discovered the file would load if the last part of the query was removed: d=1595788270. If you just edit the url, the browser automagically downloads the file for you.
The code grabs all of the stylesheet links, find the right one (by checking if it includes xenforo) and lops off the last query variable.
I'm not sure what that query variable does, but the file loads properly without it for me.
sorry for the delay, we are trying to sort it out
some cloudflare fuck-up <.<
not sure what has happened.
i've completely disabled the replacement for css and js files for the time being.
Also i've started the transition to an geo-aware setup - as well as trying out some more caching (with cloudflare)
I'm not sure if this will have other problems, like cf writing us, that we are using too much bandwidth; if this is the case, i will disable cf-caching for attachements again.
also static files will be moved to the new cdn-domain if everything will work out, the way I hope it will.
If this transition is sucessfull i will enable geo-DNS.
Also i'm now going to monitor the site a bit more - sorry for any inconvenience. I didn't expect that much problems with changing frontend-servers
not sure what has happened.
i've completely disabled the replacement for css and js files for the time being.
Also i've started the transition to an geo-aware setup - as well as trying out some more caching (with cloudflare)
I'm not sure if this will have other problems, like cf writing us, that we are using too much bandwidth; if this is the case, i will disable cf-caching for attachements again.
also static files will be moved to the new cdn-domain if everything will work out, the way I hope it will.
If this transition is sucessfull i will enable geo-DNS.
Also i'm now going to monitor the site a bit more - sorry for any inconvenience. I didn't expect that much problems with changing frontend-servers
rewrite disabled, till i find a solution for this problem ...
edit
enabled attachment-rewrite again.
edit
again some errors - fixing it now ...
edit
regex fixed. Please report all errors
edit 2020/11/23
too much traffic for cloudlare free... so lets see what i can find elsewhere...
Last edited:
mhm. i'm re-enabeling the URL again.
But actually it should not occure anymore, since i've disabled the change to this domain o.o
thanks for posting.
But actually it should not occure anymore, since i've disabled the change to this domain o.o
thanks for posting.
CSS just took its regular biweekly holidays. I was not aware that CSS Union has negotiated paid time off for its members with Akiba server..?
The site layout it completely broken for me. I almost didn't find the "log in" button because the whole layout is fucked up. Site looks really broken on my end.