Jump to content

KazVee

Moderators
  • Posts

    846
  • Joined

  • Days Won

    24

KazVee last won the day on June 24

KazVee had the most liked content!

About KazVee

  • Birthday 01/01/1875

Profile Information

  • Gender
    Female
  • Interests
    π‘―π’†π’π’Šπ’π‘―π’π’”π’• π‘Ύπ’Šπ’Œπ’Š ✨ https://wiki.helionet.org ✨ π‘»π’†π’„π’‰π’π’Šπ’„π’‚π’ 𝒅𝒐𝒄𝒔, 𝒔𝒖𝒑𝒑𝒐𝒓𝒕 π’ˆπ’–π’Šπ’…π’†π’”, 𝒂𝒏𝒅 π’”π’†π’“π’—π’Šπ’„π’† π’Šπ’π’‡π’

Recent Profile Visitors

57,428 profile views

KazVee's Achievements

Experienced

Experienced (11/14)

  • Very Popular Rare
  • Posting Machine Rare
  • One Year In Rare
  • Conversation Starter Rare
  • Collaborator Rare

Recent Badges

117

Reputation

  1. I did a bit more digging after my post, but thanks for confirming I was looking in the right place! πŸ™‚ For the short answer: When you link to your files, instead of using "http://" in the link, use "https://" with the s in there, that seems to be where the issue is, because your site is running on https (which is always good to do) and so you should link to files also on https. For the longer explanation about how we investigated this and why it's happening: When I tested out your download links, at first Chrome told me it blocked the download because the files could be "potentially dangerous, suspicious, unverified, or insecure". That doesn't single out your files specifically, just that zip files on the internet can sometimes be risky to download, so there's that built-in protection in the browser. After that happened a few times, when I clicked on the Download link... nothing happened, just like you reported. When I pressed F12 in Chrome to bring up the DevTools (and F12 to close them again, if you tried it just now! πŸ˜„) that's a handy way to see what's happening inside the browser with requests. I've highlighted the relevant clue. Your website, on https, was linking to a (potentially) "insecure" file, since you only used "http" in the link for the file. So the browser's built-in protection kicked in and blocked the download, and then eventually just blocked it silently, so it looked like nothing was happening. If you change your links to start with "https://" and the rest of the filepath, you'll be linking from your secured website to a secured file, and the downloads should work again and not get blocked by the web browser. Please give that a try and let us know if it still gives you trouble after that! πŸ™‚
  2. Please could you give us the website address of the site you're having trouble with, we can't really troubleshoot this issue from an image. I checked your message history and found URL https://wildabyss.heliohost.us/WAA.php and looked around in there, but didn't find a Downloads page to check. Once we have more details we'll be able to try to replicate the issue from here and offer any advice we can. The Bad Gateway messages sound related to Apache Restarts, you can read more about them here: https://wiki.helionet.org/502_Bad_Gateway
  3. This support request is being escalated to our root admins.
  4. This support request is being escalated to our root admins.
  5. This support request is being escalated to our VPS admins.
  6. Hello! We have some user-generated guidelines in our Wiki that you can find here about creating a MySQL (MariaDB) database, please give this a try and let us know if you get stuck: https://wiki.helionet.org/MySQL
  7. I've made all the changes for you. Please note that it may take up to 2 hours for the domain changes to take effect. 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 Since there is a risk of data loss when main domains are changed, we made a full account backup for you before the domain was initially added, in case you need any files from before things were switched around. You can download the backup here: https://heliohost.org/backup If you're not sure how to extract the backup files, please follow our how-to guide here: https://wiki.helionet.org/Account_Backups
  8. There is no account named Serpic000, Ambot, or associated to the email addressed used on your forum account. Please post from a forum account associated to the same email address as on your HelioHost account, or provide the HelioHost account name so we can assist you further. Thanks!
  9. There is no account named Serpic000, Reps&Motions (we don't allow ampersands in account names anyway), or associated to the email addressed used on your forum account. Please post from a forum account associated to the same email address as on your HelioHost account, or provide the HelioHost account name so we can assist you further. Thanks!
  10. Looks like this person did manage to make an account after all. πŸ™‚ I'll mark this as [Solved].
  11. You joined the forum back on January 6, 2010 so you've been with HelioHost quite a long time! πŸ˜„
  12. We have a guide here on how to set up email inside Hestia control panel running on a VPS: https://wiki.helionet.org/VPS_Email Please give that a try and let us know if you get stuck.
  13. If you want to use HelioHost's nameservers, please use ns1.heliohost.org and ns2.heliohost.org. We have a guide here on how to set things up in Namecheap: https://wiki.helionet.org/Namecheap_DNS_Records For the VPS email issue, I'll drop some info in the other thread you raised for that here: https://helionet.org/index/topic/64883-vps-ubuntu-email-conf/
  14. I've added confesshub.heliohost.us to your account for you, the other domain is not available. 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
  15. I have added heliosinfosystem.com to your account. The complete URL you asked for of heliosinfosystem.com/bid-e is a path and cannot be added to accounts. If you want the heliosinfosystem.com/bid-e path to redirect to your main domain, you could use an htaccess redirect. 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 it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
×
×
  • Create New...