Notices by alenshore (anonymous6479@ryona.agency), page 2
-
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:47:17 JST alenshore @dcc @mint That's it tho for now. Might be my internet. Might just take forever to federate. Also, older posts don't federate to you right? Only once you've added a relay (in this case fixed some probs) then everything after right? -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:45:57 JST alenshore @mint @dcc Also did you get my post? I am not getting my post.
I am also getting a lot more dot errors:
04:43:49.284 [error] Process #PID<0.6111.0> raised an exception ** (KeyError) key :ap_id not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map (pleroma 2.6.0) lib/pleroma/web/mastodon_api/views/conversation_view.ex:27: Pleroma.Web.MastodonAPI.ConversationView.render/2 (pleroma 2.6.0) lib/pleroma/web/views/streamer_view.ex:140: Pleroma.Web.StreamerView.render/3 (pleroma 2.6.0) lib/pleroma/web/streamer.ex:315: Pleroma.Web.Streamer.push_to_socket/2 04:43:49.285 [error] Process #PID<0.6110.0> raised an exception ** (KeyError) key :ap_id not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map (pleroma 2.6.0) lib/pleroma/web/mastodon_api/views/conversation_view.ex:27: Pleroma.Web.MastodonAPI.ConversationView.render/2 (pleroma 2.6.0) lib/pleroma/web/views/streamer_view.ex:140: Pleroma.Web.StreamerView.render/3 (pleroma 2.6.0) lib/pleroma/web/streamer.ex:315: Pleroma.Web.Streamer.push_to_socket/2 #PID<0.6110.0> raised an exception ** (KeyError) key :ap_id not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map (pleroma 2.6.0) lib/pleroma/web/mastodon_api/views/conversation_view.ex:27: Pleroma.Web.MastodonAPI.ConversationView.render/2 (pleroma 2.6.0) lib/pleroma/web/views/streamer_view.ex:140: Pleroma.Web.StreamerView.render/3 (pleroma 2.6.0) lib/pleroma/web/streamer.ex:315: Pleroma.Web.Streamer.push_to_socket/2 -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:45:56 JST alenshore @dcc @mint WAIT YES I SEE ME AND A POST I MADE FOREVER AGO!! -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:43:47 JST alenshore @mint @dcc Yay! But this appears to be an issue with more than you. I can pull an alt from another instance but I cannot talk to it. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:37:17 JST alenshore @dcc @mint Whatever is causing the connection to timeout, I don't know. It's getting pretty late. I should probably go to bed soon. If you notice anything, let me know and I'll get back to you ASAP. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:36:58 JST alenshore @mint @dcc Alright. Let me try some of the other instances I've already tried. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:30:01 JST alenshore @dcc @mint Okay. So here are the errors I get now when I attempt to message myself:
04:27:28.304 [error] Error while fetching https://ryona.agency/objects/7498bd8e-0e1c-4e5b-b0aa-f5739104767e: {:error, :timeout} 04:27:28.304 [warning] Couldn't fetch "https://ryona.agency/objects/7498bd8e-0e1c-4e5b-b0aa-f5739104767e", error: nil 04:27:59.608 [warning] Can't find LRDD template in "https://ryona.agency/.well-known/host-meta": {:error, :timeout} 04:28:19.237 [error] Process #PID<0.4811.0> raised an exception ** (KeyError) key :ap_id not found in: nil. If you are using the dot syntax, such as map.field, make sure the left-hand side of the dot is a map (pleroma 2.6.0) lib/pleroma/web/mastodon_api/views/conversation_view.ex:27: Pleroma.Web.MastodonAPI.ConversationView.render/2 (pleroma 2.6.0) lib/pleroma/web/views/streamer_view.ex:140: Pleroma.Web.StreamerView.render/3 (pleroma 2.6.0) lib/pleroma/web/streamer.ex:315: Pleroma.Web.Streamer.push_to_socket/2 04:28:38.420 [error] Could not check origin for Phoenix.Socket transport.Obvi some of these are just warnings, but figure I should include them.
-
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:27:36 JST alenshore @mint @dcc I can also turn your relay up in a search, but not myself. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:25:55 JST alenshore @mint @dcc Indeed. The error is gone and search is finally turning up results (yay!). When I click though, nothing shows. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:25:11 JST alenshore @mint @dcc Actually I found a pleroma document on the subject. Set timeout to 1000 and 10 searches for unauthenticated users (or all users I think because I don't have a different value for auth users) -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:22:38 JST alenshore @mint @dcc Lets fix the arithmatic errors first I think. What am I supposed to set and where do I set it? In the ratelimiters section there are two boxes for numbers but I don't know what to put there. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:16:00 JST alenshore @mint @dcc Well the usual complaining about how localhost isn't on the allowed domains list (I fix later) but I did get some odd ones:
03:30:04.873 request_id=F5lRXlK1Sc25OLwAAEgB [error] Could not decode user at fetch http://rawrxd4mden7rmbobaftao3qjyxbrvj4rrooehkqxlqcsdtnnn2hndid.onion/internal/fetch, :timeout 03:32:52.502 request_id=F5lRhoOcK9JzbZEAAEND [error] Internal server error: %ArithmeticError{message: "bad argument in arithmetic expression"} 03:32:52.503 [error] #PID<0.3695.0> running Pleroma.Web.Endpoint (connection #PID<0.3694.0>, stream id 1) terminated Server: {}:80 (http) Request: GET /api/v2/search?q=https%3A%2F%2Fryona.agency%2Fobjects%2F1c79d22c-7008-4001-b981-b31d1e5d1f8e&resolve=true&with_relationships=true ** (exit) an exception was raised: ** (ArithmeticError) bad argument in arithmetic expression (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter/limiter_supervisor.ex:49: Pleroma.Web.Plugs.RateLimiter.LimiterSupervisor.check_interval/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter/limiter_supervisor.ex:28: Pleroma.Web.Plugs.RateLimiter.LimiterSupervisor.add_or_return_limiter/2 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:253: Pleroma.Web.Plugs.RateLimiter.initialize_buckets!/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:170: Pleroma.Web.Plugs.RateLimiter.check_rate/1 (pleroma 2.6.0) lib/pleroma/web/plugs/rate_limiter.ex:104: Pleroma.Web.Plugs.RateLimiter.handle/2 (pleroma 2.6.0) lib/pleroma/web/mastodon_api/controllers/search_controller.ex:5: Pleroma.Web.MastodonAPI.SearchController.phoenix_controller_pipeline/2 (phoenix 1.6.16) lib/phoenix/router.ex:354: Phoenix.Router.__call__/2 (pleroma 2.6.0) lib/pleroma/web/endpoint.ex:5: Pleroma.Web.Endpoint.plug_builder_call/2But I don't think I searched for anything since I started it....
-
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:12:23 JST alenshore @mint @dcc I don't see that post you'll have to forgive me. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:09:09 JST alenshore @mint @dcc Also it says I don't have the fetcher for some reason ** (UndefinedFunctionError) function Pleroma.Object.Fetcher.fetch_object_from_id/1 is undefined (module Pleroma.Object.Fetcher is not available) Pleroma.Object.Fetcher.fetch_object_from_id("http://ryona.agency/objects/asdasdasdas")
-
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:06:54 JST alenshore @mint @dcc What do I fetch? Like a post? Do I just enter the whole URL there or? -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:06:32 JST alenshore @mint @dcc It wasn't. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 21:05:50 JST alenshore @mint @dcc I suppose I'm already in this far! It is getting kind of late though so I'll have to sleep soon. -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:59:37 JST alenshore @mint @dcc >You could also try ditching privoxy entirely and put Tor's proxy port instead
Just for the instance you mean? Because when I did that I got checkout error when attempting to add relays. Of course those were clearnet at the time so do you think it will help? -
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:57:04 JST alenshore @mint @dcc I believe this is everything. I left anything I could think was relevant in:
config :pleroma, :activitypub, [follow_handshake_timeout: 1500] config :pleroma, :feed, [post_title: %{max_length: 500, omission: "..."}] config :pleroma, :frontend_configurations, [pleroma_fe: %{alwaysShowSubjectInput: true, background: "/images/city.jpg", collapseMessageWithSubject: true, disableChat: false, greentext: true, hideFilteredStatuses: true, hideMutedPosts: true, hidePostStats: false, hideSitename: false, hideUserStats: false, loginMethod: "password", logo: "/static/logo.svg", logoMargin: ".1em", logoMask: true, minimalScopesMode: false, noAttachmentLinks: false, nsfwCensorImage: "", postContentType: "text/markdown", redirectRootLogin: "/main/friends", redirectRootNoLogin: "/main/all", scopeCopy: true, showFeaturesPanel: true, showInstanceSpecificPanel: false, sidebarRight: false, subjectLineBehavior: "email", theme: "pleroma-dark", webPushNotifications: false}] config :pleroma, :http, [proxy_url: "127.0.0.1:8118"] config :pleroma, :http_security, [enabled: false] config :pleroma, :instance, [federating: true, federation_incoming_replies_max_depth: 150, federation_reachability_timeout_days: 14, public: true] config :pleroma, :modules, [runtime_dir: "/home/pleroma/modules"] config :pleroma, :mrf, [policies: [Pleroma.Web.ActivityPub.MRF.TagPolicy, Pleroma.Web.ActivityPub.MRF.InlineQuotePolicy, Pleroma.Web.ActivityPub.MRF.HellthreadPolicy, Pleroma.Web.ActivityPub.MRF.StealEmojiPolicy]] config :pleroma, Pleroma.Web.Plugs.RemoteIp, [enabled: false] config :pleroma, :rate_limit, [search: {"", 0}, timeline: {500, 3}, app_account_creation: {1800000, 25}, relations_actions: {10000, 10}, relation_id_action: {60000, 2}, statuses_actions: {10000, 15}, status_id_action: {60000, 3}, authentication: {60000, 15}]My bad about socks btw. I forgot I turned it off because it was so long ago. :0500:
It doesn't look to appear to be on in the dumped config, which would jibe with what the webUI is telling me but let me know if I missed something.
-
alenshore (anonymous6479@ryona.agency)'s status on Monday, 20-Nov-2023 20:49:33 JST alenshore @mint @dcc Okay. Let me do that but in the meantime here was my old config with the port updated to privoxy's (because that's how it's set now anyways):
# Pleroma instance configuration # NOTE: This file should not be committed to a repo or otherwise made public # without removing sensitive information. import Config config :pleroma, Pleroma.Web.Endpoint, url: [host: "{}.onion", scheme: "http", port: 80], http: [ip: {127, 0, 0, 1}, port: 4000] config :pleroma, Pleroma.Repo, adapter: Ecto.Adapters.Postgres, prepare: :named, parameters: [ plan_cache_mode: "force_custom_plan" ] # Configure web push notifications config :web_push_encryption, :vapid_details, subject: "mailto:na@na.na" config :pleroma, :database, rum_enabled: false config :pleroma, :http, proxy_url: {:socks5, :localhost, 8118} # Enable Strict-Transport-Security once SSL is working: config :pleroma, :http_security, enabled: false config :joken, default_signer: "(HIDDEN)" config :pleroma, configurable_from_database: true