This site can’t be reached. 192.168.151.126 took too long to respond.

[AliZahir819]

Platform

Virtual Machine

bndiagnostic ID know more about bndiagnostic ID

ass

bndiagnostic output

No response

bndiagnostic was not useful. Could you please tell us why?

I can't find the answer of my issue

Describe your issue as much as you can

Hi everyone. when i run my application in vm. following error occur. This site can’t be reached192.168.151.126 took too long to respond. Try:

Checking the connection Checking the proxy and the firewall [Running Windows Network Diagnostics](javascript:diagnoseErrors()) ERR_CONNECTION_TIMED_OUT

why this error occur? and how can i recover my website?

[florence0239]

Platform

Virtual Machine

bndiagnostic ID know more about bndiagnostic IDMyLowesLife

ass

bndiagnostic output

No response

bndiagnostic was not useful. Could you please tell us why?

I can't find the answer of my issue

Describe your issue as much as you can

Hi everyone. when i run my application in vm. following error occur. This site can’t be reached192.168.151.126 took too long to respond. Try:

Checking the connection Checking the proxy and the firewall Running Windows Network Diagnostics ERR_CONNECTION_TIMED_OUT

why this error occur? and how can i recover my website?

Hello,

The ERR_CONNECTION_TIMED_OUT error typically indicates a communication problem between your browser and the server. Let’s explore some possible solutions to resolve this issue:

Check Your Connection: Ensure that your internet connection is stable. Sometimes network issues can cause timeouts. Try accessing other websites to verify if the problem is specific to your VM or the entire network. Disable Firewall and Antivirus Software Temporarily: Firewalls and antivirus programs can sometimes block connections. Temporarily disable them and check if the issue persists. Flush/Renew DNS: Open the Command Prompt (Windows + R, then type cmd). Run the following command to flush the DNS cache: ipconfig /flushdns

Change DNS Servers: Consider using alternative DNS servers (such as Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1). Update your DNS settings in your network adapter properties. Check Your Hosts File: Make sure there are no incorrect entries in your hosts file that might be causing the issue. The hosts file is located at C:\Windows\System32\drivers\etc\hosts. Check the DNS of Your Domain: If you’re trying to access a specific domain, ensure that its DNS records are correctly configured. Confirm Port Configuration: If your application runs on a specific port (e.g., 8080), verify that the port is open and accessible. Check your firewall settings to allow traffic on the required port. Inspect Tomcat Configuration (if applicable): If you’re using Tomcat, ensure it’s listening on the correct IP address. Edit the server.xml file and set the address attribute in the Connector string to your VM’s IP address. Example:

<Connector port="8080" protocol="HTTP/1.1" address="IP_address" /> Check VM Configuration: Confirm that the VM allows HTTP traffic (port 80 or 8080) in its configuration. Restart Services and VM: Restart the Tomcat service (if applicable) and your VM.

Hope this work for you.

Best Regards, florence023

[jotamartos]

Hi @AliZahir819,

Please access the VM's console and ensure that all processes are running and that the IP is the correct one

sudo /opt/bitnami/ctlscript.sh status
sudo ifconfig

[krina234pestro]

Hello,

The “ERR_CONNECTION_TIMED_OUT” error typically indicates that your browser is unable to establish a connection to the server within a specified time.

Restart the VM and the host machine. Clear your browser cache and cookies. Try accessing the site from a different browser or device to rule out browser-specific issues.

I hope this info helpful to you.

Best regard Maxim Time Clock

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.