I am working on a web app on http://pagesage.page and have deployed with Digital Ocean on a Docker container with gunicorn and meinheld with A and AAAA name records set up. Additionally, the appropriate ports for http have been set up for listening and responding.
Unfortunately, while the page responds to curl, ping, and ping6 requests, the page only ever loads on the Safari browser (and some IE distributions) and I can't seem to figure out why (I get DNS timeout errors whenever I try to load the page in Chrome or Firefox).
I've tried accessing the page from different machines (brand new and old), reset the DNS settings a few times, and reset the browser's cache, all with no success.
Does anyone have ideas or suggestions, or has anyone else encountered this same problem?
You have a problem with your SSL/TLS terminaison. The website is available on HTTP but unavailable on HTTPS. Chrome and FF redirect the user to the HTTPS version. It looks like the port 443 (used for HTTPS) is closed.
Related
i'm trying to make public my moodle site but without success.
First, i tried with the port forwarding from my router but it doesn't connect to the server, so i can imagine that there is a block from my router (i also free the port from the firewall in windows and internally the private_ip:8080 is working).
So i tried with ngrok but when i click the link from safari/chrome with my phone (on 4G) the connection gave me the error 303 see other and redirect me to localhost:8080 that of course my phone did not recognise.
Is there anyone that was able to exposed the moodle site with success?
Thank you
I have a web application written in ASP.NET MVC 5. I simply can open it from the browser with this localhost:14920 in my computer, but I want to access the same application from my Android device's browser while my laptop and Android device are in the same network. I don't know how to access it from Android.
Note: when I type 127.0.0.1 in the Android browser I can access the IIS server, but when I type 127.0.0.1:14920 it prints Bad Request - Invalid Hostname. How can I fix this issue?
You can configure IISExpress for remote access
http://www.ryadel.com/en/iis-express-allow-external-requests-remote-clients-devices/
or just change the hosting to IIS as the earlier commenter mentioned.
Try with replacing 127.0.0.1 with your IPv4 address.
I have used ngrok in the past, when needing to hit my development machine, or have someone else hit it. It is a very useful tool and very simple to install.
Once you download it, it's just a simple command line:
https://ngrok.com/docs#expose
ngrok http 80
(That is for traffic on port 80) Since your port above looks different it would be:
ngrok http 14920
That will give a URL that you can hit or any machine or device.
I have an ssl certificate(Geotrust) installed to IIS 8, listening on port 443 and running on windows server 2012-r2. This works when I access https://myapp.example.com and it shows me the standard IIS page. My problem is that I am trying to connect to the parse-server(nodejs, express) running on serverUrl: http://localhost:1337/parse. So when trying to connect to https://myapp.example.com:1337/parse
chrome says: "myapp.example.com finished the connection unexpectedly" and I cant reach the expected site.
ios-simulator says: kCFStreamErrorDomainSSL, -9806.
The connections to http works as expected on the urls described above.
I have tried to set the SSL port to 1337(and portforward 443->1337 on my router), but then I can not start the parse-server on the same port.
First time doing this, so really gratefull if anyone can point me in the right direction!
Solved by doing an reverse proxy in IIS 8.
I needed two applications in IIS and downloaded them like this: yourSite->right-click middle pane->"install application from gallery" and search & download these:
Download URL Rewrite (i downloaded 3.0)
Application Request Routing
This helped a lot:
http://weblogs.asp.net/owscott/creating-a-reverse-proxy-with-url-rewrite-for-iis
I'm trying to run a webapp on localhost (port 9000) which talks to an API, also on localhost (port 8882). This works fine in Chrome, FF and IE9, but in edge, every XHR yields the following error message:
XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due to error 00002efd
I've tried setting internet security settings to the lowest level, and adding localhost to the trusted sites, but without results.
Why am I getting this error, and how can I get around it?
I don't know why, but switching the API to port 9001 instead of 8882 fixed the problem. By the way, I ran into a similar issue on Safari on Mac, solved by the change as well.
I have running my own website for security reasons at an unusual port: https on Port 11223 instead oh 443.
This website provides the feature to login with an google account, realized by using the google OAuth API.
At the last step of authentication (redirecting back from google OAuth to my system), an network timeout happens.
On the other hand: if my server is running https on default port 443 instead of 11223, everything works fine.
I have configured the google OAuth client settings (Redirect URIs, Home page URL, JavaScript origins) for using the special port 112233. But without success.
Maybe it's important to know, the Server is behind a firewall with NAT. This means, the firewall receives https connections to port 11223 to redirect this to the internal webserver running https only on port 11223. But I think, this is not the point.
What could be the reason, why port 443 works but port 11223 doesn't.
I guess google OAuth does not support webservers running on an unusual prot!?!
The port number is 16 bits and thus can not exceed 65535.
Could it be proxy configuration issues? I recommend you configure your firewall to return 404 on the port 11223 and see what happens.