Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

#SelfHosting week 0, phase 1B: DNS records settings.

Uncategorized
2 2 0
  • week 0, phase 1B: DNS records settings. Performed @_elena 's instructions on her "self hosting for newbies" part 2. Except for the post-install as I run it through terminal and not through web UI. For an ms-dos-born it's easier to perform a simple command such as "yunohost tools postinstall" rather than go to web, then type, then search for the various UI elements.
    Everything went smooth, except for letsencrypt at first. But in the end it seems to have worked. It got stuck because hostinger panel didn't get one suggested parameter, the numeric 3600, every record has a parameter which is 3, 4 or 5 numbers.
    Created the domain and subdomain to point it to yunohost admin interface, and then obstacle came.
    Opening browser to subdomain, just returns "connection timed out".
    Checked for nginx parameters through yunohost terminal, using the desired Sudo commands.
    Then, "sudo yunohost diagnosis run"
    "sudo yunohost diagnosis show --issues --human-readable"
    and I got explanation on reverse dns which was wrong.
    After that, I searched on the web (and on AI, I admit) the position on hostinger panel to set them, and I found "set tpr record"
    placed the desired domain name.
    And now it's time to wait for propagation. But what about the "connected timeout", in the article posted in blog.elenarossini.com no such obstacle was mentioned.
    I'm back to my 20s when I spent the night (it's almost 4 in the morning), learning commands.
    Last but not least, accessibility issue: I'm using an app called WebSSH pro, downloaded on app store. Set it up, and VoiceOver for iOS does not read the keys I press on keyboard so I'm very slow to type commands there. Pc is better. In a few hours I'll try hostinger's terminal.
    UPDATE: I have just found I set one DNS wrong, now I'll wait for it to propagate. Next update in some hours. I placed a useless number. Such as 72.162 (wrong) instead of 72.62 (right).
    Like when you start developing on your own and everything crashes due to a missing semicolumn in a string of code.

  • week 0, phase 1B: DNS records settings. Performed @_elena 's instructions on her "self hosting for newbies" part 2. Except for the post-install as I run it through terminal and not through web UI. For an ms-dos-born it's easier to perform a simple command such as "yunohost tools postinstall" rather than go to web, then type, then search for the various UI elements.
    Everything went smooth, except for letsencrypt at first. But in the end it seems to have worked. It got stuck because hostinger panel didn't get one suggested parameter, the numeric 3600, every record has a parameter which is 3, 4 or 5 numbers.
    Created the domain and subdomain to point it to yunohost admin interface, and then obstacle came.
    Opening browser to subdomain, just returns "connection timed out".
    Checked for nginx parameters through yunohost terminal, using the desired Sudo commands.
    Then, "sudo yunohost diagnosis run"
    "sudo yunohost diagnosis show --issues --human-readable"
    and I got explanation on reverse dns which was wrong.
    After that, I searched on the web (and on AI, I admit) the position on hostinger panel to set them, and I found "set tpr record"
    placed the desired domain name.
    And now it's time to wait for propagation. But what about the "connected timeout", in the article posted in blog.elenarossini.com no such obstacle was mentioned.
    I'm back to my 20s when I spent the night (it's almost 4 in the morning), learning commands.
    Last but not least, accessibility issue: I'm using an app called WebSSH pro, downloaded on app store. Set it up, and VoiceOver for iOS does not read the keys I press on keyboard so I'm very slow to type commands there. Pc is better. In a few hours I'll try hostinger's terminal.
    UPDATE: I have just found I set one DNS wrong, now I'll wait for it to propagate. Next update in some hours. I placed a useless number. Such as 72.162 (wrong) instead of 72.62 (right).
    Like when you start developing on your own and everything crashes due to a missing semicolumn in a string of code.

    @elettrona I'm sorry you had these issues Elena! I wish I could help you out in person...

    The first time around, a year ago, I remember having to wait 2 full days for DNS records to correctly propagate... which seems ridiculously long now.

    DNS was my only issue then, everything else went smoothly.

    Now with a year of practice on my back, I can set things up in minutes.

    The joke "it's always DNS" is pretty appropriate.

    Super proud of you for doing all this!


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti