(ArgumentError) Postgrex expected an integer in -9223372036854775808..9223372036854775807, got <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1>>. Please make sure the value you are passing matches the definition in your table or in your query or convert
(ArgumentError) Postgrex expected an integer in -9223372036854775808..9223372036854775807, got <<0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1>>. Please make sure the value you are passing matches the definition in your table or in your query or convert the value accordingly.
(pleroma) deps/postgrex/lib/postgrex/type_module.ex:715: Pleroma.PostgresTypes.encode_params/3
(postgrex) lib/postgrex/query.ex:45: DBConnection.Query.Postgrex.Query.encode/3
(db_connection) lib/db_connection.ex:1079: DBConnection.describe_run/5
(db_connection) lib/db_connection.ex:1150: anonymous fn/4 in DBConnection.run_meter/5
(db_connection) lib/db_connection.ex:592: DBConnection.prepare_execute/4
(ecto) lib/ecto/adapters/postgres/connection.ex:86: Ecto.Adapters.Postgres.Connection.execute/4
(ecto) lib/ecto/adapters/sql.ex:256: Ecto.Adapters.SQL.sql_call/6
(ecto) lib/ecto/adapters/sql.ex:542: Ecto.Adapters.SQL.struct/8
The exact stacktrace above is from executing
mix pleroma.user reset_password luckydonald
But this gets also spammed in my log while the frontend recieves 500
s.
I rebuild the instance to switch out a config :pleroma, Pleroma.Web.Endpoint
> secret_key_base
which got leaked accidentally.
It may be that config :web_push_encryption, :vapid_details
> public_key
and private_key
changed too, I'm not quite sure about those being even filled before.
I rebuild, now basically nothing is working.
My setup is similar to this docker approach.
Edited by luckydonald