New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Thank for the update.
Here is my token: d159-a3c8-db5f-66aa
Something is wrong: https://im.ge/i/image.orWEk1
At least open the network tool in browser and see what is happening for that missing css? 404? 500? Timeout? CDN not reachable? CERT outdated/hijacked?
bunnyCDN reports a few 5xx errors, however I can't confirm this with the monitoring currently.
I switched on the perma-cache so stuff is getting stored within the bunnyCDN network, so if a cache has nothing stored, it pulls it from there instead of every time from the origin webserver.
This should reduce the 5xx errors.
Likely its is related to the AntiDDoS (serverius) and for some reason, the requests from BunnyCDN seem to get blocked from time to time.
I will ticket them, will see.
sorry, I was sure webmaster will immediately know what the problem is as soon as the incident is reported, no point for me to venture guesses.
4cd6-d1d1-d3d0-a296 is the token.
dc9b-e970-b4f8-abaa
df3c-4c58-773d-ada4
Third try, setup does not proceed further than the token: 10b3-033b-483b-4f3c
wait, like a long time on the screen VERY LONG and it will work
So I tested it, using your account name and the tokens you posted.
I tired it 6 times, I expected 6 times, that the system would find and confirm your token.
It didn't, the first time It did jump over your post, the second time it grabbed it, the 3rd time it jumped over your post. Afterwards it grabbed it every time.
I suspect some broken cache, or something else related.
I can't explain this as of now, I post when I have a fix or workaround.
I have same problem.
No rush, I only wanted to help testing, not to use it
Maintenance Announcement
Melbourne and Los Angeles will be rebooted Sunday Evening 23:00 CEST
fa98-b490-52c1-8328
6e0a-0042-bbe6-0422
pw reset lul
So it is working now?
7368-16ee-3d90-98b3
Its not broken, its not as reliable as it should be.
I still need to patch it when I get time to make it more reliable.
Works if you wait long enough :P
I have tried a few browsers but only text ones load due to low ram.
The IPv6 is not the one indicated, took the one in the container and works. Buster.
Thank you for your efforts for the community
If a /64 is available on the location, you get one randomly assigned.
You can in theory use any IPv6 address in that range you like.
However, the Panel yet dosen't ask LXD for the IPv6 it assigned to the Container, hence it dosen't know which IPv6 address the container has.
Except, you have only a /70, then it works as displayed, since its automatic static configuration.
At some point in the future the panel will sync the data with LXD.
So, that /64 is allocated only to me? i.e. no conflicts possible if by an astronomical chance or because i want to have a beef with the cafe?
Yes.
Every container get its own /64 or /70, plus own gateway.
Same goes for NAT IPv4.
91d5-0858-f610-e7b5
Thanks!
Addendum to the Outages Yesterday until today Morning.
The Antwerp DC had several power outages according to Novos.be
This resulted in about 15 hours of downtime.
Services are back up and running since 14 hours about 09:16 CET.
I have registered for a account with token - 0cef4816786930dd8c5500e438106b1e82b677fe
Reading is an essential skill.
Check and read the rules before applying.
e96f-da3c-462e-b60e
Speedrun spamming threads with useless bullshit replies until you get to 50 posts. Good one.
Rolled and smoked