Jump to content

KazVee

Chief Information Officer
  • Posts

    1408
  • Joined

  • Days Won

    47

Everything posted by KazVee

  1. Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.
  2. Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.
  3. Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.
  4. The OP hasn't replied in over 2 weeks so I'll mark this thread as Inactive. @akbaig, if you're still having issues connecting to your DB, please let us know by raising a new support ticket. Thanks!
  5. I've just checked the mjsbakery site and it loads. I'll close this thread since the OP hasn't replied in over 2 weeks. If the website still doesn't load after clearing your cache (https://wiki.helionet.org/Clear_Your_Cache), please let us know by raising a new support ticket. Thanks!
  6. An account reset will wipe the entire account, and reset it back to the defaults as if it was a brand new account. We cannot exclude a database from an account reset. If you want your account wiped, please make a backup of your database and any other files you will need. Make sure you download the backup to your local machine, don't just leave it in Plesk since it'll get wiped from there during the reset. You can find more information about how to create and download an account backup in our technical documentation Wiki here: https://wiki.helionet.org/Account_Backups Please let us know once you've made and downloaded your backup, so we can start the reset process for you.
  7. This support request is being escalated to our root admins.
  8. Please note, due to current issues with the Johnny server, we cannot currently make any of the above domain changes. You can read more about it in the News section here: https://helionet.org/index/topic/67733-when-it-rains-it-pours Thanks for your patience and apologies for the inconvenience.
  9. This support request is being escalated to our root admins.
  10. This support request is being escalated to our root admins who have the DNS magic. 🙂
  11. I've added those domains to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
  12. Do you want ITEBWP401S25HW.helioho.st or ITEBWP401S25HW.heliohost.us, or is it a .com or a .net? When requesting domains, please provide the following information: Your hosting account username The full addon domain name you want, including the top-level domain (TLD): If you're using HelioHost's domains, specify either helioho.st or heliohost.us If you've purchased a custom domain, specify the TLD (such as .com, .net, etc.) You can see a reminder of all the information needed in our technical documentation Wiki on this page: https://wiki.helionet.org/Addon_Domains#How_can_I_create_an_Addon_Domain?
  13. Those domains have been added for you. Please note, they will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains
  14. This support request is being escalated to our root admins.
  15. This support request is being escalated to our root admins who can fix the DNS.
  16. I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
  17. This support request is being escalated to our root admins who can set up remote access.
  18. This support request is being escalated to our root admins who can fix the DNS issue for you.
  19. This support request is being escalated to our root admins who can fix the DNS issue.
  20. I've now removed the butangfindr domain from your account as requested.
  21. As it's been over a week, I will go ahead and mark this request as [Solved] so it's clear to all unpaid volunteer staff which user requests are still pending. If you decide to proceed with the account reset, please let us know in a new support request thread that you want the addon domain to be your new main domain, and that you're ready for the required account reset to accomplish this. Thanks!
  22. I've added laptoprecordsmanager.helioho.st to your account for you. Please note that it may take up to 2 hours for the domain change to take effect. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache For the remote access part of your request, please can you confirm which database user name you want to have remote access? For remote access, our root admins need to know your hosting account username, database name, and the database user name you want to have access. - Hosting account username: dipeshshrestha - Database name: lrmdatabase - Database user name you want to have remote access: Please confirm? You can find the details required by the admins in our technical documentation Wiki here: https://wiki.helionet.org/PostgreSQL_Database_Remote_Connection_Error#How_to_Request_Remote_Access_to_PostgreSQL
  23. This support request is being escalated to our root admins who can fix the DNS.
  24. The root admins will reply in here once it's been fixed. As you can read in the News section here (https://helionet.org/index/topic/67623-when-servers-explode/) there have been server problems recently, but for these DNS issues, they are trying to action them as quick as they can.
×
×
  • Create New...