Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
This might be a very basic question but I've been stucked for 2 days
I've bought the domain name AAA.xyz on Namecheap and I have my Golang web server running on my port :8095 (I've redirected my ports on my router so my server is accessible from everywhere with my public IP http://93.6.XXX.YYY:8095/)
How do I make my Namecheap domain name point to my IP adress with the right port so when I enter AAA.xyz on my browser I get response from my API ?
You have to edit your namecheap DNS settings to add an A Record, which will point to your server IP. That's enough to divert all traffic to your domain, to your server.
Although, unless it's not a production setup, it'd be better to let a reverse proxy server like nginx handle the incoming http traffic. Then you won't have to expose your port to the outside world either. (Unless you want to).
Install nginx. Add a proxy pass to your nginx config file which will route all requests coming to port 8095 to your application at 127.0.0.1:8095.
This will also help you when you have multiple go apps running on your server on different ports. You can use different URLs to point to different apps.
e.g. https://yourdomain.com/app1 will go to 127.0.0.1:8095
and https://yourdomain.com/app2 will go to 127.0.0.1:8096
Bonus: You can use Letsencrypt to provide your nginx server with an HTTPS certificate for free and then all communication with your applications will be happening through port 443 on HTTPS, without configuring every app to handle the certificate.
Also, open ports 80 and 443 in your firewall.
If you need any help with a specific step. I'll expand on that.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Debian 9.11 box...
I have two REST APIs written in Go running on server on ports 8111 and 8112 (both as services) and an Apache2 server running on default port 80.
My Web application (written using Quasar/VueJs) is served by the Apache2.
My internet domain points to this box.
I cannot access the APIs using www.mydomain.com:8111/...
In fact, when I use these things by IP and without HTTPS everything worked. Now that I'm trying to use the domain name and HTTPS ("magically" provided by Cloudflare) I can't acess anything...
What am I missing?
Solved!
On Apache <VirtualHosts> configurations:
<Location /api/userstatus >
ProxyPass http://localhost:8111/userstatus
ProxyPassReverse http://localhost:8111/userstatus
</Location>
Incoming traffic uses HTTPS, internal API uses HTTP.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Probably has been asked before.
I've set up an FTP server in IIS on an Windows 8 machine using the following steps:
Installed IIS FTP services
Set a static public IP and a static internal LAN IP, set up Router
Created a new FTP site in IIS manager
created a root ftp folder, gave test_user r/w permissions
Required SSL, selected self-generated certificate
Entered the static LAN ip of my machine, used port 21
Enabled Basic authentication
Allowed authorization for "selected user": test_user
Logged successfully as test_user into the ftp server from within the local network.
Remoted to an outside server, browsed to [publicip]:21 and ftp://[mypublicip]
FAIL
Troubleshooting
Tried to access the FTP server from another PC on the LAN using the [PublicIP]:[PortNumber]
Turned off Windows firewall
No SSL
Basic Authentication, same test_user
Connected my computer directly to WAN, without router (I have an ethernet line to WAN, no modem - so I could just plug in the cable)
tried a different port for the FTP server (1342)
checked my public IP
remoted to the same server, tried browsing for my FTP again
went through several combinations of the above steps. at one point, the combination contained all of the troubleshooting steps.
FAIL
So no matter what I did, I could not access the FTP server remotely. Really mystified.
What could I have done wrong? Can the ISP block FTP even if you use non-standard ports?
Turns out you can access the FTP server when connected directly to the modem. I accidentally forgot to change site bindings (wrong ip) in IIS before changing the network connection. Of course I still can't connect through the router, with the firewall disabled. The issue is the router (or maybe Im an idiot) and I can't find any solution aside from trying another router.
Is your router translating the public IP down to the internal lan IP? This is typically done through a NAT rule in the router to tell it where to send the public traffic to inside your network.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a web side hosted on IIS, windows 8 os. I can access from my browser to this page via these urls:
localhost/mysamplesite
192.168.21.10/mysamplesite
I can ping my ip address like this: ping 192.168.21.10
But I can not ping to 192.168.21.10/mysamplesite this command gives error: ping request could not find host 192.168.21.10/mysamplesite
Actually have another machine (192.168.21.45) that installed apache banchmark on. I want to test request from apache banchmark to my site. So I can not send request.
ab -n 1 -c -1 192.168.21.10/mysamplesite
This does not work.
As arco444 mentioned, you can't ping a website, just a computer itself.
ping is the first thing to try when troubleshooting network connectivity problems
ping 192.168.21.10
from the remove machine.
You can also try PsPing to test for connectivity to a certain port:
psping 192.168.21.10:80
however you can not use this to check for a particular resource on your web site.
Instead you have to use a tool to test for http traffic, Apache Benchmark is one of them, depending on the OS on the remote machine, there are many other tools.
If ping works, check the firewall settings on your Windows 8 machine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Im trying to use a proxy with firefox, but the issue is that some sites are getting my real ip.
-If I enter to http://www.showmemyip.com it shows me the proxy ip.
-If I enter to http://www.whatismyip.com it shows me the proxy ip + "No proxy detected"
-If I enter to http://whatismyipaddress.com/proxy-check it shows me the proxy ip + "Proxy server not detected." + everything on false (green)
How can it be possible that they are detecting my ip? I saw that flash doesnt use the proxy configured on firefox... but the pages that Im trying to access dont have any flash script.
Is there any way of being 100% that they would only see the proxy ip and not mine?
Thanks!
That because the proxy pass your ip to server in http header(detail), you should setup the proxy to anonymously.
There are some Java and Flash hacks to find out the visitor's real IP even behind a proxy server. As for Java you can turn it off forever. For Flash install some browser extension to be able to block it when you need. Use this site for tests: http://mylocation.org
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have a Heroku app and I've add a CNAME (www to herokuapp) to redirect it from GoDaddy to Heroku. Now I'm trying to manage also the naked domain.
This is from Heroku documentation.
Naked domains (also known as bare domains or apex domains, for example mydomain.com) must use DNS A-records. To setup your root domain, add separate A records for each of the following addresses using your DNS management tool:
75.101.163.44
75.101.145.87
174.129.212.2
Check that your DNS is configured correctly with the “host” command:
$ host example.com
example.com has address 75.101.163.44
example.com has address 75.101.145.87
example.com has address 174.129.212.2
I've also activated the forwarding from the GoDaddy main menu.
Ok, if I try host example.com with my domain, all is ok.
But, when I try with the browser, I get this:
Heroku | No such app There is no app configured at that hostname.
Perhaps the app owner has renamed it, or you mistyped the URL
I tried also with the command heroku domains:add yourdomain.com
but this create a second instance of my app, it doesn't redirect it to the full domain www
Heroku highly advises against using A-records to point domains at cloud apps. Using A-records increases the chance of instability for DNS resolution. Heroku goes into details here.
Instead, you should redirect your naked domain to the 'www' subdomain. You can refer to this SO thread for more details on how to set that up on GoDaddy.