Home>

I'm deploying a rails6 application of my own domain on heroku with a paid plan of 7 dollars a month.

I don't know if the server is down for 20 to 30 minutes exactly once a day (several times when it is a lot), but I cannot access the site.

I've made a little improvement by adding an add-on for heroku's scheduler, but I want to make sure there is no time when I can't access the site.

For heroku, are there times when I can't see them?

And how can I get rid of the time I can't see the site?

I'm sorry to say that i am ignorant.

  • Answer # 1

    I want to make sure there is no time when I can't access the site.

    As you may know, the Hobby plan cannot always operate.
    Since it takes about once every 24 hours to restart, it is necessary to use two or more Dynos if it is always required.
    *While restarting, you will not be able to access the site.

    You can add heroku scheduler add-on to make it restart at midnight or early in the morning, but be careful as the scheduler itself does not run correctly.

    The cycling happens once every 24 hours (plus up to 216 random minutes, to prevent every dyno for an application from restarting at the same time).
    [Translation of deepl.com]
    Cycling is done once every 24 hours (plus a random amount of up to 216 minutes to prevent all dynos in the application from restarting at the same time).
    Reference: https://devcenter.heroku.com/articles/dynos#restarting


    "Not safe" or "Privacy mess"

    If this is displayed, please set up SSL.
    This is free for Hobby plans.
    (If you can not use it, please check if the plan is reflected.)


    If the above is performed and the following is displayed even if the cause is squeezed for the time being, I think that a solution will come out if you present the error log etc. at that time.

    "A part of your name dot com is displayed"

  • Answer # 2

    For heroku, are there times when I can't see them?

    That shouldn't be the case due to Heroku. Of course, I think that it will happen very rarely due to heroku trouble, but it should not happen that there are times when you cannot see it regularly.
    Heroku is restarting dyno once a day, but it should have been able to access the site. At least it didn't happen in my environment.

    And how can I get rid of the time I can't see the site?

    As mentioned above, I don't think that the state where the site cannot be accessed has occurred due to Heroku, so
    It is a cause that makes me suddenly think that the memory is insufficient due to the application or some error continues to occur,
    In any case, I think that no measures can be taken until the cause is investigated after investigating the state that says "I cannot access the site".