Using the host's fail2ban instead of the crazymax/fail2ban container
Using dedicated ports instead of traefik
Removing the https redirections
Looking for the requirements, I was surprised to see that nobody talks about the versions of fail2ban that are compatiblles with fail2rest
Moreover, I don't really understand where the fail2rest sessions are secured... Shouldn't the environment variables containing the credentials be shared across the fail2web and fail2rest containers ?
Expected behavior
I suppose the ajax call is supposed to return 200 ?
Docker (please complete the following information):
Docker version 20.10.8, build 3967b7d
docker-compose version 1.24.0, build 0aa59064
Desktop (please complete the following information):
Ubuntu 18.04
Smartphone (please complete the following information):
Same behavior on all devices.
Additional context
Here is the docker-compose file :
Describe the bug
The fail2rest service always respond 404.
To Reproduce
Using this docker-compose file given below, the fail2rest service will always respond 404.
Especially, the ajax call from the https://fail2web.XXXXXX/ to https://fail2rest.XXXXXX/api/global/status responds 404.
What I aldready tried
Moreover, I don't really understand where the fail2rest sessions are secured... Shouldn't the environment variables containing the credentials be shared across the fail2web and fail2rest containers ?
Expected behavior
I suppose the ajax call is supposed to return 200 ?
Docker (please complete the following information):
Desktop (please complete the following information):
Smartphone (please complete the following information): Same behavior on all devices.
Additional context Here is the docker-compose file :