dr_robotBones

joined 7 months ago
[–] dr_robotBones@reddthat.com 1 points 6 months ago (1 children)

I don't have any firewalls, and https://206.x.x.x and the internal IP one both worked.

[–] dr_robotBones@reddthat.com 1 points 6 months ago

The external IP is properly bringing me to the portfolio, its just the subdomain that now seems to be blocked.

[–] dr_robotBones@reddthat.com 1 points 6 months ago (1 children)

It does. I think my subdomain is being blocked by ISPs.

[–] dr_robotBones@reddthat.com 0 points 6 months ago

I've done further testing with external network connections. I'm getting a Blocked hosts error, it seems my subdomain is being targeted by ISPs.

[–] dr_robotBones@reddthat.com 1 points 6 months ago (3 children)

I get a 206 address that matches my server's public IP. My laptop is on the same network as the portfolio, but I did test external connections using a mobile hotspot, which resulted in me successfully connecting to the IP address with telnet, but not being able to connect to the domain name. On my phone's browser, while on data, I was able to access my portfolio website using the public IP address as the URL, rather than the domain name.

[–] dr_robotBones@reddthat.com 1 points 6 months ago (1 children)

I don't think it is, but its hard to tell for sure.

[–] dr_robotBones@reddthat.com 1 points 6 months ago (1 children)

Yeah the DNS' public IP matches my server's. The access logs have some connections from the SSL validation and from when I successfully connected using the public IP address. The error logs are empty.

[–] dr_robotBones@reddthat.com 1 points 6 months ago

I did it this way because I didn't think a randomly generated domain name from cloudflare would be professional enough. I might have to go with that if I can't get this working though.

[–] dr_robotBones@reddthat.com 1 points 6 months ago* (last edited 6 months ago)

The error was: ERR_CONNECTION_TIMED_OUT. I also got an ERROR_CONNECTION_REFUSED earlier.

[–] dr_robotBones@reddthat.com 2 points 6 months ago

Yes, that's what I did.

[–] dr_robotBones@reddthat.com 1 points 6 months ago (5 children)

I can't connect to the domain at all. I think the certificate problem was because I was connecting with the IP address rather than the domain name.

30
submitted 6 months ago* (last edited 6 months ago) by dr_robotBones@reddthat.com to c/selfhosted@lemmy.world
 

I'm trying to self host my portfolio on an old laptop running Ubuntu server. I've successfully set up docker and nginx. I got a DNS subdomain from freedns.afraid.org.

The IP connected to the DNS matches my server's public IP address.

I can connect with https://mypublicip/ from outside the network, but it shows as an insecure connection and the https has lines going through it in the browser.

Any attempts to connect to the website via DNS have failed, and trying to connect via IP on port 80 fails as well. I really have no clue what is going on, let me know if you need more information, or if this is the wrong place to ask for help with this sort of thing.

Edit: Whatever problem I had before, it seems its been fixed. However my subdomain is being blocked by ISPs. Thank you for the help everyone, I'll probably have to do cloudflare tunneling instead of fully self-hosting it.

view more: next ›