The start.sh script uses pgrep to find the PID of nginx to determine its status. Unfortunately, pgrep sometimes detects nginx processes running on virtual machines or different operating systems, leading to incorrect assumptions about nginx's status on the target system.
How to reproduce?
# On a system where nginx is correctly running
./usr/share/bunkerweb/scripts/start.sh start
pgrep nginx
# Output: PID(s) of nginx if running on the target system
# On a different OS, running a separate nginx instance
pgrep nginx
# Output: PID(s) of nginx from a different OS, not relevant to our target system
Configuration file(s) (yaml or .env)
No response
Relevant log output
No response
BunkerWeb version
1.5.9
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
[X] I have removed all private data from the configuration file and the logs
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What happened?
The start.sh script uses pgrep to find the PID of nginx to determine its status. Unfortunately, pgrep sometimes detects nginx processes running on virtual machines or different operating systems, leading to incorrect assumptions about nginx's status on the target system.
How to reproduce?
Configuration file(s) (yaml or .env)
No response
Relevant log output
No response
BunkerWeb version
1.5.9
What integration are you using?
Docker
Linux distribution (if applicable)
No response
Removed private data
Code of Conduct