Replies: 1 comment
-
|
Your configuration looks correct. Another way to express it would be access_rules:
s2s:
- deny:
- server: "bad-server.rs"
- allow
s2s_access: s2sIdea A) The option documentation says:
One explanation is that maybe I don't see any other option that could block incoming s2s connections. If that option does not apply, then there's no solution right now. Idea B)
Maybe connections are blocked to your XMPP server "yourserver.org", but are allowed to your MUC service "muc.yoursever.org" ? Looking at In your ejabberd.log file do you get lines like this? Or does it look like this? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been going to multiple issues here on GitHub, which however were mostly around a decoade old and didn't appear to correspond to the current version of ejabberd anymore. I would like to know how to effectively block s2s (federations) with specific servers. My current attempt is the following one:
However, it doesn't appear that federation is successfully blocked, as I can still se visitoros from blocked servers joining the MUC.
Happy for any help with this!
Beta Was this translation helpful? Give feedback.
All reactions