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
Related
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.
I have a developed a web application based on asp.net mvc 4 framework and it works fine in visual studio. since we want to launch our website to public we bought a domain from the godaddy account. And in GoDaddy -> Domains -> Manage -> we mapped the domain name to public/external IP address e.g. 178.112.24.5 ( which is different from what i get in cmd-> ipcoonfig-> shows 192.168.0.2). I guess i should use the public ip addresss not the local ip address shown in the cmd -> ipconfig.
Now i created a web site under iis-> sites-> add new site -> mynewdomain -> with protocol as http, ipaddress as unassigned(default) , port as 80 and hostname as www.mynewdomain.com . But whenever i launch this site from iis, it routes to ISP router configuration login.html page(BTW i use Rogers Internet). So it also fails to launch from other network computers and chrome shows the error as ERR_CONNECTION_REFUSED.
I followed some posts on this site:
How to solve ERR_CONNECTION_REFUSED when trying to connect to localhost running IISExpress - Error 502 (Cannot debug from Visual Studio)?
https://serverfault.com/questions/54623/sites-in-iis-not-available-externally
I tried to fix this by defining firewall rule for port 80 (selected domain,private and public ) , dnsflush and some suggestions from the above two links. But it didn't fix the issue.
You want host your app yourself, ok.
So:
1. To access your host from other networks you've open ports (80 for http and ) in your firewall, sure your local IP address will 192.168.0.2 and you can access your app from LAN on it. But others must get your external IP.
2. Next moment is your domain resolver, you must setup your Name Servers for your host external IP address.
Now what can you do:
First of all use DMZ for testing, it will be open all connections to your machine, but after testing setup your firewall and open only nessessary ports.
And if your internet provider gives you your external IP + not blocking connections you can host your application.
Sure this way of host your web site is not recommended because:
A. Windows 10 Home is not server OS.
B. You need minimum 100 MB/s Speed.
C. Not secured to use home router as firewall.
Hope this will help you.
I have a rails app running on standard port 3000. I can access it from localhost:3000 just fine, but I want to access it from my LAN address as well. (http://192.168.1.x:3000). When I try to use the LAN IP in my browser, I get a connection refused error. I am using POW (http://pow.cx/), which may be the culprit, but cannot sort how. I CAN access http://192.168.1.x which delivers the default pow landing page, so it seems like the IP resolution is working, but for some reason not on the port my app is serving on.
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.
I have started the Ruby on Rails tutorial and am on my first app. I did all of this on an instance I have on amazon web service (aws). A while ago I installed apache on there so when I put in the public address (port 80) it tells me 'It works'. I want to access this server from my web browser at home.
However when I put in the server address :3000 (the port the app should be running at) I get nothing. Do I need to tell the box to open port 3000 or something of the like?
You need to open the instance's security group to accept traffic on port 3000. Check out the docs for more information.