Jump to content

closer1

Members
  • Posts

    30
  • Joined

  • Last visited

Posts posted by closer1

  1. 2020 Server Improvements
     
    Good morning,
     
    thanks for your effort on maintaining HelioHost and continuously improving it.
     
    I´ve made a donation via PayPal to put it towards the fundraiser.
     
    Transaction-ID: 2V5989876K370884P
     
    HelioHost username: somedays
    heliohost server: tommy
    heliohost main domain: somedays.heliohost.org

     

     

  2. That IP and port are still whitelisted in Tommy's firewall, and your site seems to be working fine for me.

    Currently, my nodejs application access is still corrupted as above (There are times when the access does not appear error).

    I am trying to find the cause. Can you give me a log of my nodejs application.

    I tried blocking all outbound connections on my local environment and I got the following error

    image3ec1c8223df41dfa.png

     

    I tried blocking port 27017 on my local environment and I got the following error
    image6c5f1c302a2a8518.png
     

    My MongoDB is stored as "Replica Set - 3 nodes" so when the primary node (104.40.21.132:27017) fails to connect, it will redirect to the other two nodes but the firewall will block it. 

    So can you please add secondary node ip 104.40.21.243 and 138.91.174.29 to the whitelist in Tommy's firewall.

    Thanks very much

  3. TCP port 27017 has been opened to 104.40.21.132 on Tommy's firewall.

     

    It looks like your site is working now. https://vnu.hdhquangnam.tk/

    The "Incomplete response received from application" error reappeared while accessing my NodeJS application. Please let me know if the firewall allows access to "104.40.21.132" with port 27017.

    If you allow access via ip as above, please add access by allowing access via domain name (cluster0-shard-00-00-6habu.azure.mongodb.net).

    Thanks very much.
  4. The ip is the ip that your script tries to connect to. For instance if the database was hosted on Tommy the ip would be 65.19.143.6.

     

    The port is the port that your script tries to connect to. For instance if you were using mysql on the default port it would be 3306.

    IP: 104.40.21.132

    Domain Name: cluster0-shard-00-00-6habu.azure.mongodb.net

    Port: 27017

    Thanks you!

  5. Mentioning that you're connecting to a remote mongodb database would have saved me like 45 mins. All outbound ports are closed unless you request access. The reason any pages with database connections are timing out is because you never requested permission to access a remote database so the firewall is blocking you. I'm honestly a little annoyed with you right now for wasting my time.

    I tried uploading the page to heroku. Everything on it works as I expected.

    I think I have granted remote database access to my mongodb database.

    Please help me . Thank you

  6. Mentioning that you're connecting to a remote mongodb database would have saved me like 45 mins. All outbound ports are closed unless you request access. The reason any pages with database connections are timing out is because you never requested permission to access a remote database so the firewall is blocking you. I'm honestly a little annoyed with you right now for wasting my time.

    I apologize for not stating the problem. Can you help me open the firewall in this case?

    Thank you very much

  7. The first time your node application is accessed it will take a little longer to load, but it will cache the website and subsequent visits will load much faster. After some time has passed without any page views your node application will automatically uncache itself to reduce load and memory usage on the server. If you make changes to your application, and find that the changes aren't appearing when you view the page in your browser it is because an older version of your site is cached. You can force your node application to restart and load any changes by doing the following:

     

    Create a /tmp directory inside your node application directory.

     

    /home/username/node/tmp

     

    Inside that /tmp directory create a file named restart.txt.

    Now refresh your browser and the changes should show up.

     

    Here’s another note from this site that I just found earlier when I did some dig on Google:

     

    https://airbrake.io/blog/http-errors/304-not-modified

     

    @Heliohost Teams: delete this if I get it wrong, I’m learning new things. :D

    The page that returns status_code 304 is the correct page for me

  8. [Tue Apr 14 02:27:16.955758 2020] [core:error] [pid 58236] [client 65.19.143.5:63355] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://vnu.hdhquangnam.com/beta
    
    Try renaming or deleting your .htaccess.

     

    Thank you so much, it worked.
    but when I edit it does not change and continue to run the old code. I have created the file as instructed "Inside that /tmp directory create a file named restart.txt." 
  9. /home/somedays/beta/ doesn't even exist. Try the guide again. The very first step is

    Create a new directory in your home folder named node. Make sure this node directory is NOT in your public_html folder.

     

    /home/username/node

     

    I tried it but it was over 2 hours and it still isn't working.
     
    Untitledaaa07ac479f3572f.png
×
×
  • Create New...