If you clean installed Hestia 1.4.3 and cannot curl, file_get_contents, readfile etc. then, just proceed with the following steps (There is ABSOLUTELY no need to change config files, just a host file).
So let’s go!
1. Login to your server 2. Type in “nano /etc/hosts” without the quotes of course 3. Goto the last line, and add the following
Didn’t help? Hmm, try going to your php.ini configuration by navigating to: Hestia > Server Settings > nginx > Configure PHP > Advanced Then, scroll down, or just use find and type in “allow_url_fopen”, and set it to On
As I told the issue is caused by the fact that nginx only listen external_ip:80 and not to 127.0.0.1 Don’t know why and usually it doesn’t matter as you connect to a api it is usual on a external server…
And if you adjusted the config file to listen %web_port%;. Assign the template to the website / domain.
And reload Nginx and you are done.
But if you treat me. You will never a quick answer…
Why go through all that hassle when you can just add the thing in hosts, just like in 1.3.5 of HestiaCP. I don’t know why is it no longer there, but you may consider adding it in 1.4.4. So people don’t crash their heads figuring out on how to fix.
I meant like it would be great if you would add it in the next version.
Check if exists IP - HOST combination
= yes? > do nothing or delete it and reboot
= no? > add it and reboot
And this is definitely better than leaving it just without it, if Proxmox overwrites it, nothing bad will happen if it still continues working.
And yes, I think my time is valuable for a credit if the fix is going to be implemented, in a manner of adding the following specific comment in each file which used my fix. For those wondering, I like to get credit for my work.
Here is the comment
Fix suggested and assisted by xwtk
This is good enough considering the fact that I researched 3 days to find the fix, and trying to figure out the whole nightmare of configurations that were obfuscated by the installer.
Hahaha! I will do the pull request right now! By the way the crediting part was a link to how Jaap says:
“I think my time is worth at least 50 euros, donate, and I will send you the code” sends PayPal donation link
As I already said in the server which I got banned from, it’s alright to ask for donations, it’s not alright to ask donations to help.
RESPONSE TO THE MESSAGE BELOW
No LOL I do not know why I got banned because I went offline after my last message and returned to see that chat gone. Also, no I wasn’t suggested to check /etc/hosts.
RESPONSE TO JAAP’S MESSAGE
You perfectly know that your software IS GOING TO BE USED BY A NEWBIE. If you are PLAIN LAZY to implement a simple code to a few scripts of yours, JUST SAY SO, DON’T COVER IT WITH SOME USELESS BS. Being honest is a more respected thing than trying to make yourself look like some professional person who just doesn’t want to provide support to stupid in their opinion questions. YOU SHOULD HAVE BEEN READY FOR ALL OF THIS. RIGHT?
I don’t even understand how you still develop the thing, from your attitude I would say someone is forcing you to develop new versions. And that you just plain don’t love this.
There was a nice slogan BlackBerry had, do what you love. If you just want to keep the project alive, it would have been better to just finish the whole thing and wait for a new OS version to come out and adapt the software for it. Not make constant updates and make yourself look like an active developer.
Clean server Ubuntu:
127.0.0.1 localhost.localdomain localhost
remote.ip web02.client2.com web02
Hetzner cloud (Ubuntu):
#Your system has configured 'manage_etc_hosts' as True.
# As a result, if you wish for changes to this file to persist
# then you will need to either
# a.) make changes to the master file in /etc/cloud/templates/hosts.debian.tmpl
# b.) change or remove the value of 'manage_etc_hosts' in
# /etc/cloud/cloud.cfg or cloud-config from user-data
127.0.1.1 test.me.com test
setting a proper hostname on your server and eventually creating the right hosts entry (esp. on natted systems) is the responsibility of the system admin ion the first place.
I even think hestia should not touch that file an intefere with possible custom records that are there for a reason.
also we won’t do such childish credit stuff, please grow up. Pull Requests which make into the product can be tracked on github. if we’d add an echo for everything and especially for all changes the devs themselves do, you could not read anything.
so please, feel free to fork Hestia and run your own version, where you can add and change whatever you like but don’t bother us any longer.