I have a strange problem, I just installed my php web site on a shared hosting, all services were working fine. But after configuring my app I just could visit my web site only once, other attempts gives:
"The server is taking too long to respond.".
But from other IP i can access, but only once, it seems all ip addressess beeing blocked after first visit(even ftp and other services get down, no access at all from the IP), can anyone help to explore this problem ? I don't think that it's my app problem, the app works fine on my local PC.
Thanks.
First thing to try would be a traceroute to determine where your traffic is being blocked.
In a windows command prompt:
tracert www.yoursharedhostingserver.com
At the moment, trying to access this address gives this:
Fatal error: Class 'mainController'
not found in
/home/myicms/public_html/core/application/crApplication.class.php
on line 181
I have tried it multiple times and it didn't block me. It might be that You have already solved this problem.
As far as I know, the behavior described by You could only be explained by a badly configured intelligent firewall. It may have been misconfigured by Your host.
If You visit a site at a certain host and suddenly You cannot access an ftp on this host, then it's either a (really bad) firewall or a (very mean) site that explicitly adds a firewall rule to ignore that address.
Some things that You might look into:
It might be something with identd too. What was the service You have configured on Your host? Was it by any chance any kind of server-controll panel (that might have an ability to controll a firewall)?
Is the blockade permanent, or does it go off after 24h, or does it only go off after rebooting the server? Does restarting some services makes the blockade go off?
Did You install any software that "protects Your server from portscanning"? It might be a bit too aggressive.
I wish You good luck in finding a source of this problem!
Chances are that if you can access it once that its actually working. The problem is more than likely in the php code than in the server.
Related
This morning I noticed that none of the web apps I am running in Azure is reachable anymore.
I first thought its an issue with Azure itself, but when I try to connect with a mobile hotspot (through my phone) everything works as expected.
The problem seems only to exist in my own LAN at home but only Azure is affected.
When I try to navigate to a website, I get the following message:
I also cannot nslookup it:
I do not have any problem with surfing the internet. All other sites work fine... but I don't even know where to start on solving this problem.
Does anybody know a tool to diagnose this? What could be wrong here...?
I did not have any issues with accessing the services yesterday.
In recent years, DNS has become the most vulnerable part of the internet, as many other components are strengthened significantly.
Like you discovered, for some unknown reasons the DNS your machine connects to failed to sync the proper Azure related records. That's not an uncommon issue if you read about how badly DNS infrastructure around the globe was maintained.
Usual solutions are,
Switch to other DNS service than your default ISP provided ones, Google/Cloudflare public DNS servers are popular, and there are many other good options.
Hack your hosts file (but that's too complicated).
Since you had no Problems yesterday, my first question is: Did you change anything in your local Network?
Maybe some new Firewall rules or maybe some entry in your Host File for testing?
When you try to access Azure with only the IP, does that work? If yes then you have to look at your DNS.(maybe try Google DNS 8.8.8.8)
I have a webpage and a little game server running on my own machine that is located at my work office.
The problem is that some people can't reach the webpage and game server, because of some network issues. The reasons are not the key, just take it (for almost all my community all things works fine, there just some troubles for a specific group).
So,
I have set up the test Droplet on Digital Ocean, with socks5 proxy installed.
https://github.com/hensly/socks5
And it all worked :) Clients that are restricted to connect directly are just using my proxy server to connect to the webpage or game server.
.
So my questions come up:
How can I limit my proxy to work only with certain IPs? Actually, I need only one IP - the IP of my server-pc, and that's it (the reserved (white) IP and domain name attached to it). Is there a way of such limitation on the proxy side? I just don't want them to use proxy for everything (mostly because there is not an unlimited Bandwidth and it could cost some extra).
Thanks <3
p.s. if you know other, more convenient ways to solve my problem, I'd appreciate it if you share your thoughts.
So before I start, I know how to open up IISExpress to the network, there's plenty of articles about this, I even wrote one. However, these approaches do have limitations - most notably the need to add bindings which I've found to be hit-or-miss and worse, breaks any code that does things based on hostname.
I am on OsX running Windows 10 inside of Parallels and earlier this week I thought I should try to get localhost forwarded into the VM in the same way that I can do with docker containers.
I got really close, but I cannot figure out the last step. Here is what I did and what I am seeing:
I temporarily disabled my firewall on Windows
I forwarded the correct port (44300 in this case) to the guest VM and rebooted it.
I ran iisexpress through the command line so that I can see the full log (I tried through visual studio as well)
What I'm seeing is that when I hit localhost:44300 from inside the VM, my site loads fine and all sorts of things are logged.
But when I hit it from the host I'm getting
HTTP Error 403. The request URL is forbidden.
There is nothing logged by iisexpress in this scenario.
However, I know that the request is in some manner getting through since if I stop iisexpress and head to localhost:44300 again on the host, I get the standard
localhost refused to connect. ERR_CONNECTION_REFUSED
The fact that iisexpress is or is not listening on that port is cascading up to the host VM therefore, but nothing else is getting through.
So I'm a bit at a loss - it almost looks kinda like a binding thing, but as far as iisexpress knows, due to the port forwarding, wouldn't this request be coming from localhost? How can it tell if it is not? Even that sounds unlikely due to the lack of log messages. Also I never see anything pop up in fiddler.
What I wonder instead if there might be some yet other windows component that sees something bound to 44300, sees an request coming over the network stack, and shuts it down. Is that a thing?
I wanted to set up a simple go server in a webhost. I acquired a domain mydomain.com and hosted it using Bluehost. Now, going through the Go tutorial, I went through this example http://tour.golang.org/#59 and it works fine on my machine. Now, instead, I want to make the HelloWorldServer work when I call mydomain.com:4000 or some other port.
What I did was ssh to my server at bluehost, install go there, then compile the server and run. But then I try to access mydomain.com:4000 and it is not found. I also tried to change "localhost:4000" to just ":4000". any ideas how to make it work ?
Any help or pointers are appreciated. (some more details: it is a shared-hosting account)
This is due to the firewall on your BlueHost server not having ports (including 4000) open on a shared hosting account, Firewall Port Restrictions
If you want to do some simple (and not so simple) web hosting, why don't you look at Google App Engine
Very new to the Self Host WebApi, but I am very impressed with its ease of use and extendability. At least through this tutorial. Everything I've done so far works on my development machine whether I use localhost, 127.0.0.1, or my LAN Ip (192.168.0.x) but I am baffled why I can't access the service from any other computer even others in the same subnet.
In short after going through the tutorial on the machine where it is running:
Browsing to
localhost:3636/api/products/
results in the expected xml return.
On another machine on the LAN browsing to:
192.168.0.x:3636/api/products/
results in a timeout
Data points for those who might know how this all interacts:
1.) My dev machine(192.168.0.x, server, host whatever you want to call it) has IIS on it; I was so paranoid it was in the way that I stopped it via the Administration GUI
2.) I have reserved the URL/Port with the following command line executions:
>netsh http add urlacl url=http://+:3636/ user=DOMAIN\USER listen=yes delegate=yes
>netsh http add urlacl url=http://192.168.0.x:3636/ user=DOMAIN\USER listen=yes delegate=yes
2.b) I've tried both of those together and individually, and tried changing the user to "everyone" to no avail
3.) I have tried to change the code in the tutorial to set the
config.HostNameComparisonMode = HostNameComparisonMode.Exact //default is Strong Wildcard
4.) I can successfully ping and tracert to 192.168.0.x from other machines on the LAN
5.) A friend recommended I setup a TCPListener and ensure I could telnet to that to eliminate the firewall as a possibility. If that logic is sound, the firewall isn't the problem
EDIT: Thanks for your help, here's another data point that I believe confirms it's not a firewall issue. I previously posted this connection when behind a rather obtuse (at least to a non Certified guy like me) Juniper Firewall/Router. I have since redone the tutorial on another machine (without IIS) on my home network and still cannot publish the service to other computers within my LAN. Any ideas?
Well it wasn't the hardware firewall, it was the windows firewall! yikes i wasted a bunch of time on that. Once I turned off the windows firewall (the code runs in an intranet anyway) everything worked.
Anyone know of a good site that explains how firewalls and wireshark interact; or i suppose that just has to be one's first test.
I would try a couple things:
First off, get rid of the HostNameComparisonMode line. That might actually disable requests coming from other machines.
If things still don't work, try getting rid of the URL ACLs and run your application as an administrator and see if that works. If that works, you may be able to add the URL ACL back on and not have to run as an administrator. You should only need the one with '+' as the hostname.
I faced the same problem when i tried to self host using OWIN. What worked for me was -
Run Visual Studio as an Admin
Remove any and all netsh urlacl port registrations that I had added while debugging this issue
Add a inbound rule to my windows firewall
I followed the instructions on this link
https://learn.microsoft.com/en-us/dotnet/framework/wcf/samples/firewall-instructions
Check out the section - To enable a port range in advance
That's it! I was able to call my api from other computers on the network.
Hope this helps...