us.forums.blizzard.com DDos attack - guess we have to wait this one out
Looks like Blizzard are under siege…note on Bnet saying they are under attack right now. Its not just D4 that is impacted.
Blizzard servers currently under DDoS attack
For at least the past four hours. Many login issues. Slow authentication, and disconnects.
Blizzard CS post: https://twitter.com/BlizzardCSEU_EN/status/1672954423973142530
For me, I have to do ‘url: “http://pictrs:8080/” ‘ instead of 127.0.0.1 in the config.hjson file
I checked this, and my lemmy.hconf file already has the host for pictrs set to http://pictrs:8080.
The only thing that has worked so far is manually unsetting my site's image icon by unsetting it directly int he Database.
Note: this seems like it has something to do with the database, and something getting royally messed up post upgrade.
After trying all sorts of network hacks and updates, I eventually just decided to backup my Postgres container, and nuke it.
With a fresh Postgres DB running along with 0.18.0, my self hosted site is back online. Of course, my local post history and all my subs are gone... but at least my site is operational again.
I'd advise anyone self-hosting to not upgrade to 0.18.0 yet.
Lemmy instance broken after upgrading to 0.18.0
This is a docker setup, so to update all I did was change the lemmy-ui and lemmy versions in docker-compose.yml. Note: downgrading to 0.17.4 results in an API error instead, and still a broken site, so downgrading does not appear to be an option.
Upgraded my instance to 0.18.0, and now there are errors in both lemmy-ui and lemmy backend.
I see federation messages processing as usual, however trying to load the UI generates a weird error in lemmy-ui, and returns "Server Error" instead of the main page.
The error in the lemmy-ui logs looks like it is trying to load the site icon via pictrs from the public facing domain, but instead trying to connect to 127.0.1.1:443 (for pictrs) and getting refused.
lemmy-ui log
undefined
FetchError: request to https://SITE_URL_REDACTED/pictrs/image/a29da3fc-b6ce-4e59-82b0-1a9c94f8faed.webp failed, reason: connect ECONNREFUSED 127.0.1.1:443
at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1505:11)
at ClientRequest.emi
Hey Ruud. Sorry, I went to post this on lemmy.ml, but their site is down. Figured I would post here instead. Apologies if it is not allowed.
Server error after updating to lemmy 0.18.0
This is a docker setup, so to update all I did was change the lemmy-ui and lemmy versions in docker-compose.yml. Note: downgrading to 0.17.4 results in an API error instead, and still a broken site, so downgrading does not appear to be an option.
Upgraded my instance to 0.18.0, and now there are errors in both lemmy-ui and lemmy backend.
I see federation messages processing as usual, however trying to load the UI generates a weird error in lemmy-ui, and returns "Server Error" instead of the main page.
The error in the lemmy-ui logs looks like it is trying to load the site icon via pictrs from the public facing domain, but instead trying to connect to 127.0.1.1:443 (for pictrs) and getting refused.
lemmy-ui log
undefined
FetchError: request to https://SITE_URL_REDACTED/pictrs/image/a29da3fc-b6ce-4e59-82b0-1a9c94f8faed.webp failed, reason: connect ECONNREFUSED 127.0.1.1:443
at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1505:11)
at ClientRequest.emi
How to get the Twin Blades of Azzinoth Transmog
- Obtain both original glaives from the original Black Temple on a Warrior, Rogue, Death Knight, Monk, or Demon Hunter
- Equip both at the same time to obtain this achievement
- Kill Illidan in the Timewalking version of Black Temple on any character (in a premade group, leader talks to Vormu to enter raid)
When Illidan dies in step 3, you will get this achievement, unlocking the transmog.
Theses steps have to be in this order. There are no exceptions.
Welcome here, and thanks for creating the CR community.
Is it Thursday yet?