Since upgrading to Mobilizon 3.2.0 the following lines are logged continuously
23:48:51.811 [info] REFUSED CONNECTION TO Mobilizon.Web.GraphQLSocket in 26µs
Transport: :websocket
Serializer: Phoenix.Socket.V2.JSONSerializer
Parameters: %{"vsn" => "2.0.0"}
I cannot find anything in the documentation about how to deal with this. How do i properly set this up in order to stop it flooding my logs?
It actually happenend with previous versions too, hadn’t noticed until upgrading and checking the log.
And it does affect the possibilities, I cannot add new categories for example. This is what happens if I enable extra categories and attempt to create a new event:
nov 01 18:43:11 dedi0149 mobilizon[248935]: 18:43:11.096 request_id=F5OQtOc6n91AvJ4AACmB [info] POST /api
nov 01 18:43:11 dedi0149 mobilizon[248935]: 18:43:11.102 request_id=F5OQtOc6n91AvJ4AACmB graphql_operation_name=EventCategories user_id=1 actor_name=@ferdi [warning] Failed to send Sentry event. Cannot send Sentr>
nov 01 18:43:11 dedi0149 mobilizon[248935]: 18:43:11.102 request_id=F5OQtOc6n91AvJ4AACmB graphql_operation_name=EventCategories user_id=1 actor_name=@ferdi [info] Sent 500 in 6ms
nov 01 18:43:11 dedi0149 mobilizon[248935]: 18:43:11.103 [error] #PID<0.7641.0> running Mobilizon.Web.Endpoint (connection #PID<0.7640.0>, stream id 1) terminated
nov 01 18:43:11 dedi0149 mobilizon[248935]: Server: bosvreugdevents.nl:80 (http)
nov 01 18:43:11 dedi0149 mobilizon[248935]: Request: POST /api
nov 01 18:43:11 dedi0149 mobilizon[248935]: ** (exit) an exception was raised:
nov 01 18:43:11 dedi0149 mobilizon[248935]: ** (FunctionClauseError) no function clause matching in Enum."-map/2-lists^map/1-1-"/2
nov 01 18:43:11 dedi0149 mobilizon[248935]: (elixir 1.15.5) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"(#Function<1.82476797/1 in Mobilizon.GraphQL.Resolvers.Config.event_categories/3>, %{id: :lezing, >
nov 01 18:43:11 dedi0149 mobilizon[248935]: (elixir 1.15.5) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
nov 01 18:43:11 dedi0149 mobilizon[248935]: (mobilizon 3.2.0) lib/graphql/resolvers/config.ex:66: Mobilizon.GraphQL.Resolvers.Config.event_categories/3
nov 01 18:43:11 dedi0149 mobilizon[248935]: (absinthe 1.7.5) lib/absinthe/resolution.ex:209: Absinthe.Resolution.call/2
nov 01 18:43:11 dedi0149 mobilizon[248935]: (absinthe 1.7.5) lib/absinthe/phase/document/execution/resolution.ex:234: Absinthe.Phase.Document.Execution.Resolution.reduce_resolution/1
nov 01 18:43:11 dedi0149 mobilizon[248935]: (absinthe 1.7.5) lib/absinthe/phase/document/execution/resolution.ex:189: Absinthe.Phase.Document.Execution.Resolution.do_resolve_field/3
nov 01 18:43:11 dedi0149 mobilizon[248935]: (absinthe 1.7.5) lib/absinthe/phase/document/execution/resolution.ex:174: Absinthe.Phase.Document.Execution.Resolution.do_resolve_fields/6
nov 01 18:43:11 dedi0149 mobilizon[248935]: (absinthe 1.7.5) lib/absinthe/phase/document/execution/resolution.ex:145: Absinthe.Phase.Document.Execution.Resolution.resolve_fields/4
And this renders it impossible to specify any category to the event.
Further investigation leads me to think that this logging is standard behavior. Not a bug.
The error with adding categories probably is not caused by it. Having a hard time understanding how to properly add new categories to mobilizon. For now have stopped trying and going with the standard categories.
I just did a fresh installation of Mobilizon v 5.1.0 and I got the same log records
feb 08 18:20:38 sjo2-fedi-mobilizon mobilizon[39449]: 18:20:38.609 [info] REFUSED CONNECTION TO Mobilizon.Web.GraphQLSocket in 32µs
feb 08 18:20:38 sjo2-fedi-mobilizon mobilizon[39449]: Transport: :websocket
feb 08 18:20:38 sjo2-fedi-mobilizon mobilizon[39449]: Serializer: Phoenix.Socket.V2.JSONSerializer
feb 08 18:20:38 sjo2-fedi-mobilizon mobilizon[39449]: Parameters: %{"vsn" => "2.0.0"}
feb 08 18:20:48 sjo2-fedi-mobilizon mobilizon[39449]: 18:20:48.298 [info] REFUSED CONNECTION TO Mobilizon.Web.GraphQLSocket in 45µs
feb 08 18:20:48 sjo2-fedi-mobilizon mobilizon[39449]: Transport: :websocket
feb 08 18:20:48 sjo2-fedi-mobilizon mobilizon[39449]: Serializer: Phoenix.Socket.V2.JSONSerializer
feb 08 18:20:48 sjo2-fedi-mobilizon mobilizon[39449]: Parameters: %{"vsn" => "2.0.0"}
This is the corresponding log record in the webserver:
0.0.0.0 - - [08/Feb/2025:12:21:22 -0600] "GET /graphql_socket/websocket?vsn=2.0.0 HTTP/1.1" 403 664 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36"
I can’t help regarding the error message. Regarding the categories, you might find some hint in this post: Supprimer des catégories préfixées, pour des categories dans un théme special
Have either of you already filed this as an issue ?
No, I have not reported an issue for this.
The logging is not really a problem and the categories are mostly unused at our instance.