iis error: localhost refused to connect, ERR_CONNECTION_REFUSED - iis

I am installing a server using IIS 7, and I succeded to install it, and access it by localhost:80 or [my IP]:80. But when I use my smartphone, when I access to [my IP]:80, I get "localhost refused to connect: ERR_CONNECTION_REFUSED". What should I do to solve this error?
I tried to restart IIS, but it didn't work.
I tried to check the log file, but there was no error.

According to your description, I guess you may not add the ip address binding for your router.
I suggest you could try to add the both public ip and vitual ip into the binding and make sure your domain is right.
More details about how to add the binding, you could refer to below image:

Related

curl: (28) Failed to connect to raw.githubusercontent.com port 443: Connection timed out

I am facing one error while installing FCL-CLI on my system (linux).
The command I have used is : sh -ci "$(curl -fsSL https://raw.githubusercontent.com/onflow/flow-cli/master/install.sh)" .
Error: curl: (28) Failed to connect to raw.githubusercontent.com port 443...NEED HELP!
Set DNS 8.8.8.8 in network will resolve this
Faced the same issue while trying to install nvm on ubuntu. Following steps solved my issue:
1)Open the /etc/hosts file using
$ sudo nano /etc/hosts
2)Enter your password.
3)Add the following IP address at the end of the file:
185.199.108.133 raw.githubusercontent.com
4)Save and close the file.
5)Now Try installing Again.
This my fix your problem.
Change from network in setting.
Open the /etc/hosts file using
$ sudo nano /etc/hosts
and then add following IP
185.199.108.133 raw.githubusercontent.com
save it and reinstall it again
For Windows Users:
Go to the Control Panel.
Click Network and Internet > Network and Sharing Center > Change adapter settings.
Select the connection for which you want to configure Google Public DNS. For example:
3.1 To change the settings for an Ethernet connection, right-click the Ethernet
interface and select Properties.
3.2 To change the settings for a wireless connection, right-click the Wi-Fi
interface and select Properties.
If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
Select the Networking tab. Under This connection uses the following items, select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) and then click Properties.
Click Advanced and select the DNS tab. If there are any DNS server IP addresses listed there, write them down for future reference, and remove them from this window.
Click OK.
Select Use the following DNS server addresses. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server, write them down for future reference.
Replace those addresses with the IP addresses of the Google DNS servers:
For IPv4: 8.8.8.8 and/or 8.8.4.4.
For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844.
For IPv6-only: you can use Google Public DNS64 instead of the IPv6 addresses in the previous point.
Test that your setup is working correctly; see Test your new settings.
Repeat the procedure for additional network connections you want to change.
Ref: [https://developers.google.com/speed/public-dns/docs/using][Configure your network settings to use Google Public DNS]
Use a VPN or go to 1.1.1.1 in your browser and use WRAP by Cloudflare. Worked for me 👍

Nextcloud with Traefik - Bad Gateway / Connection Refused

I recently installed Nextcloud over a lamp stack and want to run Traefik in front. For that, I tweaked the apache2 ports.conf to:
Listen: 127.0.0.1:180
. Now I also configured a .toml for Traefik that points to this address.
When I try to open the website, it gives me "Bad Gateway".
Trying to solve the error I searched the Traefik logs and found this:
msg="'502 Bad Gateway' caused by: dial tcp 127.0.0.1:180: connect: connection refused"
Thinking it must be a problem with trusted_proxies I configured Apache to open it's port to the public and also changed the Traefik .toml to see wheter it would work.
It did. That means that Nextcloud definetly accepts my proxy and the proxying works all good.
Problem is, It doesn't work when I configure it on localhost.
The access.log and nextcloud.log show nothing.
Any help?
Many thanks
The solution is simple, but hidden.
Traefik is a Docker container, so normally it can't communicate with services not in the docker network.
The fix is:
ip addr show docker0
Bind Apache2 to this IPv4: (my example) Listen 172.17.0.1:180 and also modify the Traefik Config.
Then Apache2 will listen on the docker0 network which containers have access to.

Node Js ssh: connect to host port 22. No route to host

Hi I in an attempt to connect to more than one aws account I did a number of stuff that has led to this error. "ssh: connect to host abc.com port 22: No route to host" I dont know what the problem is or how to solve it.
This kind of issue occurs mostly due to following reasons:
Maybe your device is not properly connected to internet. Check your internet connection and try to load again.
May be config file has incorrect information. Check your config file has correct information. Check your ssh directory and ensure that ssh key exists.

torsocks[30239]: [connect] Connection to a local address are denied

I want to open a shared folder at home for me to access at work, because most ftp is blocked by firewall I though I'd find an inventive way to access my files.
On my remote host (at home) I host a tor hidden service that will forward all traffic to port 445 (SMB).
On my workstation I want to connect to this SMB-files by using this command:
torsocks smbclient -L \\address.onion -p<port#> -N
But this seems to return following warning:
WARNING torsocks[30239]: [connect] Connection to a local address are denied since it might be a TCP DNS query to a local DNS server. Rejecting it for safety reasons. (in tsocks_connect() at connect.c:186)
Connection to address.onion failed (Error NT_STATUS_ACCESS_DENIED)
But I can't seem to figure out what causes this error, nor do I know how to fix this.
Please help thanks ;)

WebServer on EC2 returns 503/404/nothing

I have a Linux EC2 instance. Apache in installed and up, so when I'm ssh'ed to my instance and do
curl localhost
I see a webpage served by my Apache. But when I try to access this page by URL (like http://ec2-xx-xx-xx-xx.eu-west-1.compute.amazonaws.com) I get back only 503 error page on one Internet connection, 404 error page on other connection. access_log and error_log show no activity when I try to access the server by URL. I'm stuck. Please give me some tips how to solve this issue.
I guess missing logs on local hint us that http error messages returned by amazonaws.com itself not from your Apache server. Did you set the security for port TCP 80? ssh port is open as default but I am not sure for port 80
I fixed this by turning iptables off. So firewall was the problem. Thank you guys for help.

Resources