slashzero

joined 2 years ago
MODERATOR OF
[–] slashzero 1 points 2 years ago* (last edited 2 years ago)

There are a lot of issues with lemmy 0.18.0. I started a discussion on the GitHub project on some of them. Feel free to go contribute to the discussion there.

https://github.com/LemmyNet/lemmy/issues/3314

6
submitted 2 years ago* (last edited 2 years ago) by slashzero to c/worldofwarcraft
 

For at least the past four hours. Many login issues. Slow authentication, and disconnects.

Blizzard CS post: https://twitter.com/BlizzardCSEU_EN/status/1672954423973142530

[–] slashzero 1 points 2 years ago* (last edited 2 years ago) (2 children)

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.

[–] slashzero 1 points 2 years ago

And yes… I see sync issues as well. I’ve responded to some comments multiple times because I didn’t see my original response at a later time.

[–] slashzero 1 points 2 years ago* (last edited 2 years ago) (1 children)

I also added the proxy network to both lemmy-ui and pictrs, but that did not resolve the issue.

I had to manually remove the sites icon from the database for the site to start working again.

update site set icon = null where id = 1;

I’m going to try removing the proxy network and instead use pictrs:8080 on the internal network as that feels more secure.


Update: What “fixed” the pictrs issue for me was changing it from the internal address to my web site domain / external address.

Still not 100% though, plenty of other errors in the logs.

[–] slashzero 7 points 2 years ago* (last edited 2 years ago)

~~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.

 

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

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.emit (node:events:511:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:511:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}

lemmy-ui and pictrs are on the same default lemmyinternal network.

lemmy log errors

2023-06-23T21:10:03.153597Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: data did not match any variant of untagged enum AnnouncableActivities
   0: lemmy_apub::activities::community::announce::receive
             at crates/apub/src/activities/community/announce.rs:46
   1: lemmy_server::root_span_builder::HTTP request
           with http.method=POST http.scheme="http" http.host=hakbox.social http.target=/inbox otel.kind="server" request_id=35c58bff-dc83-40f7-b7f0-d885072958ab http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16
LemmyError { message: None, inner: data did not match any variant of untagged enum AnnouncableActivities, context: SpanTrace [{ target: "lemmy_apub::activities::community::announce", name: "receive", file: "crates/apub/src/activities/community/announce.rs", line: 46 }, { target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "\u{1b}[3mhttp.method\u{1b}[0m\u{1b}[2m=\u{1b}[0mPOST \u{1b}[3mhttp.scheme\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"http\" \u{1b}[3mhttp.host\u{1b}[0m\u{1b}[2m=\u{1b}[0mhakbox.social \u{1b}[3mhttp.target\u{1b}[0m\u{1b}[2m=\u{1b}[0m/inbox \u{1b}[3motel.kind\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"server\" \u{1b}[3mrequest_id\u{1b}[0m\u{1b}[2m=\u{1b}[0m35c58bff-dc83-40f7-b7f0-d885072958ab \u{1b}[3mhttp.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m400 \u{1b}[3motel.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"OK\"", file: "src/root_span_builder.rs", line: 16 }] }
2023-06-23T21:09:14.740187Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Other errors which are not explicitly handled
   0: lemmy_server::root_span_builder::HTTP request
           with http.method=POST http.scheme="http" http.host=SITE_URL_REDACTED http.target=/inbox otel.kind="server" request_id=83feb464-5402-4d88-b98a-98bc0a76913d http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16
LemmyError { message: None, inner: Other errors which are not explicitly handled

Caused by:
    Http Signature is expired, checked Date header, checked at Fri, 23 Jun 2023 21:09:14 GMT, expired at Fri, 23 Jun 2023 21:08:14 GMT, context: SpanTrace [{ target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "\u{1b}[3mhttp.method\u{1b}[0m\u{1b}[2m=\u{1b}[0mPOST \u{1b}[3mhttp.scheme\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"http\" \u{1b}[3mhttp.host\u{1b}[0m\u{1b}[2m=\u{1b}[0mSITE_URL_REDACTED \u{1b}[3mhttp.target\u{1b}[0m\u{1b}[2m=\u{1b}[0m/inbox \u{1b}[3motel.kind\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"server\" \u{1b}[3mrequest_id\u{1b}[0m\u{1b}[2m=\u{1b}[0m83feb464-5402-4d88-b98a-98bc0a76913d \u{1b}[3mhttp.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m400 \u{1b}[3motel.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"OK\"", file: "src/root_span_builder.rs", line: 16 }] }

I've also filed a bug, because I've been trying to troubleshoot this, but haven't found a solution yet.

Any help is appreciated.

[–] slashzero 2 points 2 years ago

That sounds correct to me.

[–] slashzero 15 points 2 years ago (2 children)

I wonder if these are real users or if someone wrote a script to register users via the lemmy API… 🤔

[–] slashzero 17 points 2 years ago (8 children)

I self host! Very nice having an instance all to myself.

3
submitted 2 years ago* (last edited 2 years ago) by slashzero to c/worldofwarcraft
 

Twin Blades of Azzinoth


  1. Obtain both original glaives from the original Black Temple on a Warrior, Rogue, Death Knight, Monk, or Demon Hunter
  2. Equip both at the same time to obtain this achievement
  3. 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.

[–] slashzero 2 points 2 years ago (1 children)

Too slow! 😀

[–] slashzero 123 points 2 years ago (5 children)
 

DeAndre Hopkins Watch!

3
New community! (self.patriots)
submitted 2 years ago by slashzero to c/patriots
 

Not seeing much traffic on the [email protected] community, so decided to create one here on lemmy.world.

view more: next ›