When I run docker run ... command from your Quick Start service was unavailable and looking at docker logs ejabberd showed that it complains about config, looks like you have outdated config template options.
For example inside entry trusted_network: instead of loopback: allow you have to write now allow: loopback.
Rebuilding image through docker build . didn't help, same config errors.
There were several issues inside config template, I have commented out all of them, see differences here, until it becaume at least runnable. After those modifications server started successfully and served PSI client with my user correctly.
Don't use my differences linked above straight away, they just make service runnable, but they are not a correct way to solve config issues, some experts are needed who know what modifications should be done.
I think you need to update your config template reflecting changes in recentmost version of ejabberd service.
When I run
docker run ...
command from your Quick Start service was unavailable and looking atdocker logs ejabberd
showed that it complains about config, looks like you have outdated config template options.For example inside entry
trusted_network:
instead ofloopback: allow
you have to write nowallow: loopback
.Rebuilding image through
docker build .
didn't help, same config errors.There were several issues inside config template, I have commented out all of them, see differences here, until it becaume at least runnable. After those modifications server started successfully and served PSI client with my user correctly.
Don't use my differences linked above straight away, they just make service runnable, but they are not a correct way to solve config issues, some experts are needed who know what modifications should be done.
I think you need to update your config template reflecting changes in recentmost version of ejabberd service.