The problem that the localhost page launched by Docker cannot be confirmed in the browser when the ESET firewall is operating

Purpose

--Introduce security software called ESET and solve the problem that it is not displayed when trying to display the localhost page running on Docker with a browser.

Disclaimer

--In this work, change the settings of the security software. It will be a little delicate work, so work carefully. ――When carrying out this work on a PC lent by the company, it is strongly recommended to consult with the administrator. ――The author is not responsible for any loss caused to your PC by carrying out this work. ――Please also check the links to the references listed at the end of this article.

Prerequisite information

--Start the local server of nginx with Docker that built the environment referring to the article written by my senior. -Laravel course starting with Docker-Docker edition -Laravel course starting with Docker --Laravel edition --With ESET's personal firewall "enabled", access the following on Google Chrome and when the top page of Laravel is displayed, the work is completed. - http://localhost:8080

problem

--The top page of Laravel is not displayed even if you start the Docker container with ESET's personal firewall "enabled" and access [http: // localhost: 8080](http: // localhost: 8080) with a browser.

Method

  1. Launch the ESET app.
  2. Click "Settings".

Blank_Skitch_Canvas-4.png

  1. Click "Personal Firewall".

Blank_Skitch_Canvas-6.png

  1. Click "Settings".

Blank_Skitch_Canvas-5.png

  1. Change "Automatic mode" of "Filtering mode" to "Interactive mode".

Network.png

  1. A window will appear asking if you want to allow the traffic currently being communicated. Make sure that the communication is not suspicious, select "Remember actions (create rules)", and click "Allow". Since this window is displayed for all inward and outward traffic that is currently being performed, perform the above-mentioned "permit" work or "deny" work until the window disappears.

Blank_Skitch_Canvas.png Blank_Skitch_Canvas-2.png

  1. Start the Docker container.

  2. Access the following with a browser.

  3. You will be asked to allow traffic as you did earlier, so check the contents, select "Remember actions (create rules)" and click "Allow".

Blank_Skitch_Canvas.png Blank_Skitch_Canvas-2.png

  1. Confirm that the top page of Laravel is displayed at [http: // localhost: 8080](http: // localhost: 8080).
  2. Change "Interactive mode" of "Filtering mode" to "Automatic mode".

Network-2.png

References

-Specific communication is blocked in Mac environment (when caused by "personal firewall function")

Recommended Posts

The problem that the localhost page launched by Docker cannot be confirmed in the browser when the ESET firewall is operating
[Swift5] Problem that Cell cannot be tapped when TextView is placed in TableViewCell
A story that addresses the problem that REMOTE_ADDR cannot be acquired in a cluster built with Docker Swarm + Traefik (1.7).
Fixed the phenomenon that vuetify built in Rails is not loaded when page transition is done
Avoid the problem that session cannot be acquired when canary release when upgrading from Rails 4.2.x to 5.0.x
"ClassNotFoundException" is displayed when tomcat is started in eclipse and cannot be started
When the certificate cannot be obtained by https-portal production (Response Code: 403)
How to solve the problem that it is not processed normally when nesting beans in Spring Batch
Pg_resetwal can be used to start the PostgreSQL Docker container when WAL is broken and cannot be started.
[Rails / Docker] What to do if access is denied by the browser (localhost: 3000) after adding a gem