Timeline for Can't acccess Apache using ServerName
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2020 at 8:54 | comment | added | grawity_u1686 | Yes, the entire domain name is resolved via DNS before it can even get to your Apache server. Subdomains are not automatic. | |
| May 4, 2020 at 2:58 | comment | added | Kyle |
I did some more digging after reading your comment and might know the issue. If I try to reach hostname.home.lan, I assume this is resolved in the router. And if I try to reach nextcloud.hostname.home.lan is the whole thing resolved in the router? In that case, I would need to update the router DNS to point the Nextcloud FQDN to the same hostname as the other FQDN.
|
|
| May 4, 2020 at 1:10 | history | edited | Kyle | CC BY-SA 4.0 |
Changed port 80 to 443, added ellipses to indicate commands left out
|
| May 4, 2020 at 1:05 | comment | added | Kyle | When I try to access using the server name, I get a server not found error, the same as visiting any other invalid URL. I didn't change anything in DNS. | |
| May 3, 2020 at 22:22 | answer | added | g491 | timeline score: 0 | |
| May 3, 2020 at 18:56 | review | Close votes | |||
| May 18, 2020 at 3:02 | |||||
| May 3, 2020 at 18:19 | comment | added | grawity_u1686 | What does exactly happen when you try to access the server name? (And does the name exist in DNS?) | |
| May 3, 2020 at 17:59 | history | asked | Kyle | CC BY-SA 4.0 |