WebHostingAce
Silver Pleskian
The Issue - Forwarded to devs - Docker(Redis) and Plesk Firewall
Plesk Support for this issue - Plesk Firewall deny rules do not block connections to Docker container
Problem with the above workaround - When you are using Plesk Firewall, Everytime server reboot or Plesk Restart (After auto update), The Port 6379 becomes open again.
My Solution for this issue - Bind the Redis Docker to Localhost.
1. Search for Redis Docker in Docker Image Catalog Then Click Run.
2. In the Next Step 'Run redis', Press Cancel
3. Login to SSH as Root then Run
4. Press CTRL + C to Exit.
5. In the Plesk Panel Click on Docker again. Now you will see the Redis Docker is not Running.
6. In Redis Docker, go to Settings and Tick 'Automatic start after system reboot' > 'Ok' > 'Start'
Now the Redis Docker will be Bind to Localhost and the Port 6379 will not be accessible externally.
Please let me know if you see anything wrong with my solution.
Hope this will help someone to Run Redis Docker! without having Port 6379 open.
Plesk Support for this issue - Plesk Firewall deny rules do not block connections to Docker container
Problem with the above workaround - When you are using Plesk Firewall, Everytime server reboot or Plesk Restart (After auto update), The Port 6379 becomes open again.
My Solution for this issue - Bind the Redis Docker to Localhost.
1. Search for Redis Docker in Docker Image Catalog Then Click Run.
2. In the Next Step 'Run redis', Press Cancel
3. Login to SSH as Root then Run
Code:
docker run --name=redis -p 127.0.0.1:6379:6379 redis
4. Press CTRL + C to Exit.
5. In the Plesk Panel Click on Docker again. Now you will see the Redis Docker is not Running.
6. In Redis Docker, go to Settings and Tick 'Automatic start after system reboot' > 'Ok' > 'Start'
Now the Redis Docker will be Bind to Localhost and the Port 6379 will not be accessible externally.
Please let me know if you see anything wrong with my solution.
Hope this will help someone to Run Redis Docker! without having Port 6379 open.