Please post your log: sudo docker-compose logs > lemmy_log.out.
docker-compose logs
Attaching to lemmy_lemmy-ui_1, lemmy_lemmy_1, lemmy_postgres_1, lemmy_pictrs_1
lemmy_1 | 2022-04-14T18:13:27.156466Z ERROR r2d2: could not connect to server: Connection refused
lemmy_1 | Is the server running on host "postgres" (172.25.0.3) and accepting
lemmy_1 | TCP/IP connections on port 5432?
lemmy_1 |
lemmy_1 | 2022-04-14T18:13:27.156546Z ERROR r2d2: could not connect to server: Connection refused
lemmy_1 | Is the server running on host "postgres" (172.25.0.3) and accepting
lemmy_1 | TCP/IP connections on port 5432?
lemmy_1 |
lemmy_1 | 2022-04-14T18:13:27.156777Z ERROR r2d2: could not connect to server: Connection refused
lemmy_1 | Is the server running on host "postgres" (172.25.0.3) and accepting
lemmy_1 | TCP/IP connections on port 5432?
lemmy_1 |
lemmy_1 | 2022-04-14T18:13:27.156790Z ERROR r2d2: could not connect to server: Connection refused
lemmy_1 | Is the server running on host "postgres" (172.25.0.3) and accepting
lemmy_1 | TCP/IP connections on port 5432?
lemmy_1 |
lemmy_1 | 2022-04-14T18:13:27.156824Z ERROR r2d2: could not connect to server: Connection refused
lemmy_1 | Is the server running on host "postgres" (172.25.0.3) and accepting
lemmy_1 | TCP/IP connections on port 5432?
lemmy_1 |
lemmy_1 | 2022-04-14T18:13:29.421793Z INFO blocking operation: lemmy_server::code_migrations: Running user_updates_2020_04_02
lemmy_1 | 2022-04-14T18:13:29.422781Z INFO blocking operation: lemmy_server::code_migrations: 0 person rows updated.
lemmy_1 | 2022-04-14T18:13:29.422797Z INFO blocking operation: lemmy_server::code_migrations: Running community_updates_2020_04_02
lemmy_1 | 2022-04-14T18:13:29.423481Z INFO blocking operation: lemmy_server::code_migrations: 0 community rows updated.
lemmy_1 | 2022-04-14T18:13:29.423498Z INFO blocking operation: lemmy_server::code_migrations: Running post_updates_2020_04_03
lemmy_1 | 2022-04-14T18:13:29.424052Z INFO blocking operation: lemmy_server::code_migrations: 0 post rows updated.
lemmy_1 | 2022-04-14T18:13:29.424066Z INFO blocking operation: lemmy_server::code_migrations: Running comment_updates_2020_04_03
lemmy_1 | 2022-04-14T18:13:29.424547Z INFO blocking operation: lemmy_server::code_migrations: 0 comment rows updated.
lemmy_1 | 2022-04-14T18:13:29.424564Z INFO blocking operation: lemmy_server::code_migrations: Running private_message_updates_2020_05_05
lemmy_1 | 2022-04-14T18:13:29.425111Z INFO blocking operation: lemmy_server::code_migrations: 0 private message rows updated.
lemmy_1 | 2022-04-14T18:13:29.425127Z INFO blocking operation: lemmy_server::code_migrations: Running post_thumbnail_url_updates_2020_07_27
lemmy_1 | 2022-04-14T18:13:29.425614Z INFO blocking operation: lemmy_server::code_migrations: 0 Post thumbnail_url rows updated.
lemmy_1 | 2022-04-14T18:13:29.425630Z INFO blocking operation: lemmy_server::code_migrations: Running apub_columns_2021_02_02
lemmy_1 | 2022-04-14T18:13:29.426369Z INFO blocking operation: lemmy_server::code_migrations: Running instance_actor_2021_09_29
lemmy_1 | Starting http server at 0.0.0.0:8536
lemmy_1 | 2022-04-14T18:13:29.427608Z INFO lemmy_server::scheduled_tasks: Updating active site and community aggregates ...
lemmy_1 | 2022-04-14T18:13:29.436106Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T18:13:29.436119Z INFO lemmy_server::scheduled_tasks: Updating banned column if it expires ...
lemmy_1 | 2022-04-14T18:13:29.436461Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently post_aggregates ...
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | federation enabled, host is lemmy.rollenspiel.monster
lemmy_1 | 2022-04-14T18:13:29.526423Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T18:13:29.526439Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently comment_aggregates ...
lemmy_1 | 2022-04-14T18:13:29.551893Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T18:13:29.551911Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently community_aggregates ...
lemmy_1 | 2022-04-14T18:13:29.582781Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T18:13:29.583208Z INFO lemmy_server::scheduled_tasks: Clearing old activities...
lemmy_1 | 2022-04-14T18:13:29.583864Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T18:13:31.857247Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | 2022-04-14T18:13:31.879541Z ERROR Websocket Request{trace_id=08f42408afa333c6fb90ae7ca2880306}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api_common::get_local_user_view_from_jwt_opt
lemmy-ui_1 | Inferno is in development mode.
lemmy-ui_1 | httpbase: http://lemmy:8536
lemmy-ui_1 | wsUri: ws://lemmy:8536/api/v3/ws
lemmy-ui_1 | isHttps: false
lemmy-ui_1 | No JWT cookie found.
lemmy-ui_1 | http://0.0.0.0:1234
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | complete
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Not logged in
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Not logged in
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy_1 | at crates/api_common/src/lib.rs:165
lemmy_1 | 2: lemmy_api_crud::community::read::perform
lemmy_1 | with self=ListCommunities { type_: Some("Local"), sort: Some("Hot"), page: None, limit: Some(6), auth: Some(Sensitive) }
lemmy_1 | at crates/api_crud/src/community/read.rs:93
lemmy_1 | 3: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=08f42408afa333c6fb90ae7ca2880306
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.879874Z ERROR Websocket Request{trace_id=3cd0d35aa8dc2c47e5470b9df321d779}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api_common::get_local_user_view_from_jwt_opt
lemmy_1 | at crates/api_common/src/lib.rs:165
lemmy_1 | 2: lemmy_api_crud::post::read::perform
lemmy_1 | with self=GetPosts { type_: Some("Subscribed"), sort: Some("Active"), page: Some(1), limit: Some(20), community_id: None, community_name: None, saved_only: Some(false), auth: Some(Sensitive) }
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | not_logged_in
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy_1 | at crates/api_crud/src/post/read.rs:125
lemmy_1 | 3: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=3cd0d35aa8dc2c47e5470b9df321d779
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.882039Z ERROR Websocket Request{trace_id=74a51a53b42210b79494417fbd759a0b}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api::websocket::perform
lemmy_1 | with self=UserJoin { auth: Sensitive }
lemmy_1 | at crates/api/src/websocket.rs:14
lemmy_1 | 2: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=74a51a53b42210b79494417fbd759a0b
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.882153Z ERROR Websocket Request{trace_id=c074591da7303b45b6bdcbacf1ad44d1}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api::local_user::perform
lemmy_1 | with self=GetUnreadCount { auth: Sensitive }
lemmy_1 | at crates/api/src/local_user.rs:886
lemmy_1 | 2: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=c074591da7303b45b6bdcbacf1ad44d1
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.882259Z ERROR Websocket Request{trace_id=31b40c09eb470377e7e0f0835eea4b2f}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api::local_user::perform
lemmy_1 | with self=GetReportCount { community_id: None, auth: Sensitive }
lemmy_1 | at crates/api/src/local_user.rs:848
lemmy_1 | 2: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=31b40c09eb470377e7e0f0835eea4b2f
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.883352Z ERROR Websocket Request{trace_id=7049ddc7bd34a0cc27b18db1fa057fe5}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=7049ddc7bd34a0cc27b18db1fa057fe5
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.884177Z ERROR Websocket Request{trace_id=e32d8c8161deca60b4dc8f568af8a069}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api_common::get_local_user_view_from_jwt_opt
lemmy_1 | at crates/api_common/src/lib.rs:165
lemmy_1 | 2: lemmy_api_crud::post::read::perform
lemmy_1 | with self=GetPosts { type_: Some("Subscribed"), sort: Some("Active"), page: Some(1), limit: Some(20), community_id: None, community_name: None, saved_only: Some(false), auth: Some(Sensitive) }
lemmy_1 | at crates/api_crud/src/post/read.rs:125
lemmy_1 | 3: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=e32d8c8161deca60b4dc8f568af8a069
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | 2022-04-14T18:13:31.900744Z ERROR Websocket Request{trace_id=b206e01eb70266cb069b41d02feef4d3}: lemmy_websocket::handlers: Error during message handling not_logged_in: InvalidSignature
lemmy_1 | 0: lemmy_api_common::get_local_user_settings_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:177
lemmy_1 | 1: lemmy_api_common::get_local_user_settings_view_from_jwt_opt
lemmy_1 | at crates/api_common/src/lib.rs:201
lemmy_1 | 2: lemmy_api_crud::site::read::perform
lemmy_1 | with self=GetSite { auth: Some(Sensitive) }
lemmy_1 | at crates/api_crud/src/site/read.rs:26
lemmy_1 | 3: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=b206e01eb70266cb069b41d02feef4d3
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:13:32.427995Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | 2022-04-14T18:13:33.398837Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:14:00.380110Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:14:17.727440Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:14:26.285051Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:14:42.193058Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:16:03.725092Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:16:19.149553Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:18:31.771851Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:22:39.682417Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:22:44.479282Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | {
lemmy-ui_1 | op: 'ListCommunities',
lemmy-ui_1 | data: {
lemmy-ui_1 | type_: 'Local',
lemmy-ui_1 | sort: 'TopMonth',
lemmy-ui_1 | limit: 100,
lemmy-ui_1 | page: 1,
lemmy-ui_1 | auth: undefined
lemmy-ui_1 | }
lemmy-ui_1 | }
lemmy-ui_1 | TypeError: Cannot read properties of undefined (reading 'send')
lemmy-ui_1 | at e.send (/app/dist/js/server.js:2:4637)
lemmy-ui_1 | at t.o.refetch (/app/dist/js/server.js:2:428952)
lemmy-ui_1 | at new t (/app/dist/js/server.js:2:424807)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:170:28)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:303:35)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:307:39)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:337:37)
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
postgres_1 | The files belonging to this database system will be owned by user "postgres".
postgres_1 | This user must also own the server process.
postgres_1 |
postgres_1 | The database cluster will be initialized with locale "en_US.utf8".
postgres_1 | The default database encoding has accordingly been set to "UTF8".
postgres_1 | The default text search configuration will be set to "english".
postgres_1 |
postgres_1 | Data page checksums are disabled.
postgres_1 |
postgres_1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres_1 | creating subdirectories ... ok
postgres_1 | selecting dynamic shared memory implementation ... posix
postgres_1 | selecting default max_connections ... 100
postgres_1 | selecting default shared_buffers ... 128MB
postgres_1 | selecting default time zone ... UTC
postgres_1 | creating configuration files ... ok
postgres_1 | running bootstrap script ... ok
postgres_1 | sh: locale: not found
postgres_1 | 2022-04-14 18:13:26.695 UTC [31] WARNING: no usable system locales were found
postgres_1 | performing post-bootstrap initialization ... ok
postgres_1 | syncing data to disk ... ok
postgres_1 |
postgres_1 |
postgres_1 | Success. You can now start the database server using:
postgres_1 |
postgres_1 | initdb: warning: enabling "trust" authentication for local connections
postgres_1 | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1 | --auth-local and --auth-host, the next time you run initdb.
postgres_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres_1 |
postgres_1 | waiting for server to start....2022-04-14 18:13:27.154 UTC [37] LOG: starting PostgreSQL 12.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
postgres_1 | 2022-04-14 18:13:27.157 UTC [37] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2022-04-14 18:13:27.185 UTC [38] LOG: database system was shut down at 2022-04-14 18:13:26 UTC
postgres_1 | 2022-04-14 18:13:27.196 UTC [37] LOG: database system is ready to accept connections
postgres_1 | done
postgres_1 | server started
postgres_1 | CREATE DATABASE
postgres_1 |
postgres_1 |
postgres_1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1 |
postgres_1 | waiting for server to shut down....2022-04-14 18:13:27.379 UTC [37] LOG: received fast shutdown request
postgres_1 | 2022-04-14 18:13:27.383 UTC [37] LOG: aborting any active transactions
postgres_1 | 2022-04-14 18:13:27.383 UTC [37] LOG: background worker "logical replication launcher" (PID 44) exited with exit code 1
postgres_1 | 2022-04-14 18:13:27.383 UTC [39] LOG: shutting down
postgres_1 | 2022-04-14 18:13:27.412 UTC [37] LOG: database system is shut down
postgres_1 | done
postgres_1 | server stopped
postgres_1 |
postgres_1 | PostgreSQL init process complete; ready for start up.
postgres_1 |
postgres_1 | 2022-04-14 18:13:27.489 UTC [1] LOG: starting PostgreSQL 12.10 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
postgres_1 | 2022-04-14 18:13:27.489 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2022-04-14 18:13:27.489 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2022-04-14 18:13:27.496 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2022-04-14 18:13:27.519 UTC [51] LOG: database system was shut down at 2022-04-14 18:13:27 UTC
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | {
lemmy-ui_1 | op: 'ListCommunities',
lemmy-ui_1 | data: { type_: 'All', sort: 'TopAll', limit: 20, auth: undefined }
lemmy-ui_1 | }
lemmy-ui_1 | TypeError: Cannot read properties of undefined (reading 'send')
lemmy-ui_1 | at e.send (/app/dist/js/server.js:2:4637)
lemmy-ui_1 | at t.o.refetch (/app/dist/js/server.js:2:705105)
lemmy-ui_1 | at new t (/app/dist/js/server.js:2:704730)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:170:28)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:303:35)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:307:39)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:221:20)
lemmy-ui_1 | at renderVNodeToString (/app/node_modules/inferno-server/dist/index.cjs.js:337:37)
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
lemmy-ui_1 | Only elements types base, body, head, html, link, meta, noscript, script, style, title are allowed. Helmet does not support rendering <undefined> elements. Refer to our API for more information.
postgres_1 | 2022-04-14 18:13:27.524 UTC [1] LOG: database system is ready to accept connections
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:26:04.905286Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:37:48.948788Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:38:46.520126Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: not_logged_in: InvalidToken
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_api::site::perform
lemmy_1 | with self=GetSiteConfig { auth: Sensitive }
lemmy_1 | at crates/api/src/site.rs:529
lemmy_1 | 2: lemmy_server::root_span_builder::HTTP request
lemmy_1 | with http.method=GET http.scheme="http" http.host=lemmy.rollenspiel.monster http.target=/api/v3/site/config otel.kind="server" request_id=1ce10b24-0ba2-4647-8af8-c7383009a7c7 http.status_code=400 otel.status_code="OK"
lemmy_1 | at src/root_span_builder.rs:16
lemmy_1 | 3: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 4: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 5: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 6: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/arbiter.rs" loc.line=314 loc.col=25
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 7: tokio::task::runtime.spawn
lemmy_1 | with kind=block_on task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/task/local.rs" loc.line=468 loc.col=12
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | LemmyError { message: Some("not_logged_in"), inner: InvalidToken, context: "SpanTrace" }
lemmy_1 | 2022-04-14T18:38:46.520173Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: not_logged_in: InvalidToken
lemmy_1 | 0: lemmy_api_common::get_local_user_view_from_jwt
lemmy_1 | at crates/api_common/src/lib.rs:125
lemmy_1 | 1: lemmy_server::root_span_builder::HTTP request
lemmy_1 | with http.method=GET http.scheme="http" http.host=lemmy.rollenspiel.monster http.target=/api/v3/user/banned otel.kind="server" request_id=139e753a-15fa-4fb7-a872-6fe0a5192f37 http.status_code=400 otel.status_code="OK"
lemmy_1 | at src/root_span_builder.rs:16
lemmy_1 | 2: tokio::task::runtime.spawn
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 3: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 4: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/lib.rs" loc.line=207 loc.col=5
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 5: tokio::task::runtime.spawn
lemmy_1 | with kind=local task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/actix-rt-2.7.0/src/arbiter.rs" loc.line=314 loc.col=25
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | 6: tokio::task::runtime.spawn
lemmy_1 | with kind=block_on task.name= loc.file="/root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/task/local.rs" loc.line=468 loc.col=12
lemmy_1 | at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/util/trace.rs:16
lemmy_1 | LemmyError { message: Some("not_logged_in"), inner: InvalidToken, context: "SpanTrace" }
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:38:51.641424Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:39:12.563419Z ERROR Websocket Request{trace_id=d47cd5c50caef1121edd75a56d1e5ce5}: lemmy_websocket::handlers: Error during message handling email.smtp_server needs a port, IE smtp.xxx.com:465: email.smtp_server needs a port, IE smtp.xxx.com:465
lemmy_1 | 0: lemmy_api::local_user::perform
lemmy_1 | at crates/api/src/local_user.rs:772
lemmy_1 | 1: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=d47cd5c50caef1121edd75a56d1e5ce5
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:39:53.756737Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:40:10.357897Z ERROR Websocket Request{trace_id=b8129b78f1ebd788ac18a8cd61ca32f5}: lemmy_websocket::handlers: Error during message handling email.smtp_server needs a port, IE smtp.xxx.com:465: email.smtp_server needs a port, IE smtp.xxx.com:465
lemmy_1 | 0: lemmy_api::local_user::perform
lemmy_1 | at crates/api/src/local_user.rs:772
lemmy_1 | 1: lemmy_websocket::handlers::Websocket Request
lemmy_1 | with trace_id=b8129b78f1ebd788ac18a8cd61ca32f5
lemmy_1 | at crates/websocket/src/handlers.rs:68
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:40:49.907028Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:47:01.879257Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T18:52:54.833364Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:00:00.789890Z INFO lemmy_server::scheduled_tasks: Updating active site and community aggregates ...
lemmy_1 | 2022-04-14T19:00:00.806215Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T19:00:00.806238Z INFO lemmy_server::scheduled_tasks: Updating banned column if it expires ...
lemmy_1 | 2022-04-14T19:00:00.806668Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently post_aggregates ...
lemmy_1 | 2022-04-14T19:00:00.894610Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T19:00:00.894632Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently comment_aggregates ...
lemmy_1 | 2022-04-14T19:00:00.917992Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T19:00:00.918014Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently community_aggregates ...
lemmy_1 | 2022-04-14T19:00:00.950180Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:03:12.068322Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:03:42.159872Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:07:47.450664Z INFO lemmy_websocket::handlers: 2.204.39.84 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:08:27.066555Z INFO lemmy_websocket::handlers: 2.204.39.84 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:08:34.954752Z INFO lemmy_websocket::handlers: 2.204.39.84 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:10:18.750768Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:11:25.874340Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:12:35.973139Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: WebSocket upgrade is expected.
lemmy_1 | NoWebsocketUpgrade
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:12:41.907752Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: WebSocket upgrade is expected.
lemmy_1 | NoWebsocketUpgrade
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:15:47.814433Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
lemmy_1 | 2022-04-14T19:16:10.563027Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:17:03.442077Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:17:08.287619Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:17:20.068571Z INFO lemmy_websocket::handlers: 93.212.25.246 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T19:34:46.051118Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Request error: error sending request for url (http://pictrs:8080/image): error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | Reqwest(reqwest::Error { kind: Request, url: Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("pictrs")), port: Some(8080), path: "/image", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name does not resolve" })) })
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T20:00:00.214548Z INFO lemmy_server::scheduled_tasks: Updating active site and community aggregates ...
lemmy_1 | 2022-04-14T20:00:00.229512Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T20:00:00.229529Z INFO lemmy_server::scheduled_tasks: Updating banned column if it expires ...
lemmy_1 | 2022-04-14T20:00:00.229855Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently post_aggregates ...
lemmy_1 | 2022-04-14T20:00:00.339478Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T20:00:00.339496Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently comment_aggregates ...
lemmy_1 | 2022-04-14T20:00:00.369379Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | 2022-04-14T20:00:00.369396Z INFO lemmy_server::scheduled_tasks: Reindexing table concurrently community_aggregates ...
lemmy_1 | 2022-04-14T20:00:00.400239Z INFO lemmy_server::scheduled_tasks: Done.
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
lemmy_1 | 2022-04-14T20:07:37.807997Z INFO lemmy_websocket::handlers: 85.216.8.122 joined
lemmy_1 | OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: dns error: failed to lookup address information: Name does not resolve
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
pictrs_1 | Error: Error in DB, IO error: Permission denied (os error 13)
pictrs_1 |
pictrs_1 | Caused by:
pictrs_1 | IO error: Permission denied (os error 13)
What OS are you trying to install lemmy on?
Debian 11
Any browser console errors?
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data client.js:2:1410047
handleImageUpload https://lemmy.rollenspiel.monster/static/js/client.js:2
(Async: promise callback)
handleImageUpload https://lemmy.rollenspiel.monster/static/js/client.js:2
n https://lemmy.rollenspiel.monster/static/js/client.js:2
Found a bug? Please fill out the sections below. 👍
For front end issues, use lemmy-ui
Issue Summary
I also get the message when I try to upload an icon or banner in the admin section. Like issue #1863
Steps to Reproduce
Technical details
Please post your log:
sudo docker-compose logs > lemmy_log.out
.What OS are you trying to install lemmy on? Debian 11
Any browser console errors?