0
submitted 1 year ago* (last edited 1 year ago) by dotmatrix@lemmy.ftp.rip to c/lemmy_support@lemmy.ml

So I'm currently trying to set up an instance, and I'm unable to upload pictures. The following toaster appears: https://imgur.com/d0MUhUb

And in the logs I see this:

2023-06-25T10:48:11.127198782Z 2023-06-25T10:48:11.127080Z  WARN lemmy_server::root_span_builder: Request error: error sending request for url (http://localhost:8080/image): error trying to connect: tcp connect error: Address not available (os error 99)
2023-06-25T10:48:11.127262799Z Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("localhost")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 99, kind: AddrNotAvailable, message: "Address not available" })) })

I have a pictrs container up, and set the following options in lemmy.hjson:

  pictrs_config: {
    url: "http://pictrs:8080"
    api_key: "apikey"
  }

Also tried it with pictrs_url: "http://pictrs:8080" (as described here), but that didn't help either. Why is lemmy trying to access localhost:8080 rather than pictrs:8080?

Edit: This has been resolved, thanks to @slashzero@hackbox.social: https://lemmy.ml/comment/948928

top 7 comments
sorted by: hot top controversial new old
[-] slashzero@hakbox.social 0 points 1 year ago* (last edited 1 year ago)

Are you running lemmy 0.18.0? It breaks a bunch of internal network connectivity. The short term solution is to add an external network to both the lemmy-ui and pictrs containers, then you can change http://pictrs:8080 to http://your_domain.


Note: there are also some issues in 0.18.0 with comment federation at the moment. Please reply to confirm this comment was seen, thanks!

[-] reinar@distress.digital 0 points 1 year ago

I've updated to 0.18.0 as well and can see your comment

[-] slashzero@hakbox.social 1 points 1 year ago

Yay! Thank you for confirming

[-] iKill101@lemmy.bleh.au 0 points 1 year ago

I can see your comment on my instance running 0.18.0!

[-] slashzero@hakbox.social 1 points 1 year ago

Yay! Small victories

[-] dotmatrix@lemmy.ftp.rip 0 points 1 year ago* (last edited 1 year ago)

Well, butter my butt and call me a biscuit. In implementing this, I stumbled upon an issue: I had the url in pictrs_config, when it should have been pictrs.

Now at least the logs are showing an error that matches the toaster:

2023-06-25T13:09:27.753749368Z 2023-06-25T13:09:27.753609Z  WARN lemmy_server::root_span_builder: error decoding response body: expected value at line 1 column 1
2023-06-25T13:09:27.753809022Z reqwest::Error { kind: Decode, source: Error("expected value", line: 1, column: 1) }

I already have those containers in an external network, and changing the URL hasn't fixed it.

[-] slashzero@hakbox.social 1 points 1 year ago* (last edited 1 year ago)

Oh, this span builder error. Yeah I’ve been seeing that error since I upgraded to 0.18.0. Sorry, I don’t have a solution for this one.

Glad you figured out your pictrs error though! One other thing I did was update my resolve.conf so that valid DNS hosts were making it to the containers. Also try rebooting your host.

Feel free to add to this discussion. https://github.com/LemmyNet/lemmy/issues/3314

load more comments
view more: next ›
this post was submitted on 25 Jun 2023
0 points (NaN% liked)

Lemmy Support

4659 readers
28 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS