Viewing a response to: @dimitrisp/re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t055508207z
Goddady is the registrar of the domain I'm using to test this. I've already set the A record on there to my public IP address. However, it doesn't seem to be directing queries to the test website I have on my server. Notably, I set up a DHCP reservation for my PC's internal IP, and also set up dynamic DNS for my router via noip.com since my router is assigning internal IPs dynamically and my ISP is, I believe, assigning dynamic IPs externally. So one of my questions is: I should be using the dynamic DNS address (i.e. myhostname.ddns.net), right? Don't I need to change the name server addresses on Godaddy too? I don't know why it's not redirecting to my website :/
author | gk01 |
---|---|
permlink | re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t073227278z |
category | tutorial |
json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
created | 2017-08-15 07:32:27 |
last_update | 2017-08-15 07:33:12 |
depth | 3 |
children | 11 |
last_payout | 2017-08-22 07:32:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 675 |
author_reputation | 0 |
root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 11,853,128 |
net_rshares | 0 |
I'm having trouble to keep up with your comments scattered all around my posts. Let's continue the whole discussion here. If you are trying to setup a server to your home connection, your provider might have the port 80 blocked. If you are trying to access port 80 from within your network using your public IP (= your domain), it may not work, as some routers do not do this. Try to access your server via the domain from a different network (for example, the WiFi of a neighboor, or mobile data) Edit: and ifyou have a dynamic IP, and a subdomain that is getting updated, then you should setup a CName from your domain to the DNS subdomain that gets updated with your dynamic IP
author | dimitrisp |
---|---|
permlink | re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t094431382z |
category | tutorial |
json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
created | 2017-08-15 09:44:30 |
last_update | 2017-08-15 09:45:36 |
depth | 4 |
children | 10 |
last_payout | 2017-08-22 09:44:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 682 |
author_reputation | 75,800,974,934,104 |
root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 11,863,533 |
net_rshares | 0 |
Alright, sounds good. I'll respond to your other comment here too. Yes, my ISP, I believe, blocks port 80. Every online check failed to connect with port 80 even though I manually set port 80 on my router settings to accept incoming traffic and port forwarded it. However, the online checks seem to indicate that they do not block port 443. Ahhhh, maybe that's it. I'll try accessing the website on my other computer with the VPN running. I'm not exactly sure what I'd stick in the CName or if this would even work, since doesn't the CName point to the A Record? I believe I do have a dynamic IP, but what I've done is set up a Dynamic DNS host via NOIP.com so that the domain falez.ddns.net will always be mapped to my router's public IP address, no matter what that address becomes. However, with Godaddy I cannot use falez.ddns.net as the A Record; I have to use an actual IP address, which means once my router's public IP is updated, I'll have to manually adjust the A Record. I don't imagine my router's public IP is updated often, but I'm not sure. I have the same public IP today that was assigned yesterday, so... It didn't work with a VPN and what not because I'm assuming the request gets redirected to the server before ever leaving my LAN? I just tried accessing it from another network and it works. Whoop whoop!! Fucking stoked. First ever server that I've set up. Thanks a million billion, amigo. Do you have any tutorials on setting up your own DNS and name servers?? Or do you know of any up-to-date, decent tutorials about that on the web?
author | gk01 |
---|---|
permlink | re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t185354908z |
category | tutorial |
json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
created | 2017-08-15 18:53:54 |
last_update | 2017-08-15 19:02:27 |
depth | 5 |
children | 9 |
last_payout | 2017-08-22 18:53:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,564 |
author_reputation | 0 |
root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 11,907,690 |
net_rshares | 0 |
I see you had success, so I'll just leave these replies in case anyone with the same problems as you enters my post! If your ISP blocks port 80, you won't be able to host a webserver. You may be able to host a secure webserver (https) if they don't block port 443. You have to create a CName record instead of an A record for your `www.domainnamehere.com`, that points to `falez.ddns.net`. The problem is that you won't be able to use non-www domain (`domainnamehere.com` won't work). If you don't the next time you change IP, your site won't be available. Also, some providers may take up to 48 hours to update DNS records If you connect to a VPN, you may encounter problems. Connect to a different network altogether (saw you did that), and clear your dns cache! You won't be able to setup a DNS server on your network, as most, if not all, ISPs block incoming connections to port 53 that is being used for DNS lookups. It's in my plans to write a tutorial to setup your own DNS server, I'm just looking for a nice interface to include for not so tech-savvy people.
author | dimitrisp |
---|---|
permlink | re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t203831138z |
category | tutorial |
json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
created | 2017-08-15 20:38:30 |
last_update | 2017-08-15 20:38:30 |
depth | 6 |
children | 8 |
last_payout | 2017-08-22 20:38:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,074 |
author_reputation | 75,800,974,934,104 |
root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 11,915,738 |
net_rshares | 619,520,000 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
gk01 | 0 | 619,520,000 | 100% |