Cannot download vst-install.sh #2061
Comments
|
Try this Grant access to your server if it doesn't help |
|
I think issue is because of #2060 |
|
dpeca, maybe |
Thanks, but doesn't help. |
|
|
|
@anton-reutov he just shows that the content of the file is invalid, that's why he uses cat. In the meanwhile: and you will be happy. |
|
can't reproduce on debian 9 |
I know 😂 , but with |
|
i checked on debian 9, sorry cant reproduce |
|
@kristijansoldo as written. The problem is that vesta frogot "again" to renew their domain. There are still entries in dns cache which show to the parked domain. Due to the current facts, in special they wanted to release a new patched version yesterday, I would suggest to use hestia... @anton-reutov its clearly a dns cache issue, no need to involve yourself, just renew the domain on time... |
|
@kristijansoldo download it from github: |
|
@dpeca you still should not suggest it until the exploits are closed, at least my point of view... |
|
I guess he is aware of it |
|
@ScIT-Raphael Hahaha! I have no words! Sad and funny in the same time. |
If it is an DNS cache issue c.vestacp.com/apt.vestacp.com might not work either... |
|
@jaapmarcus |
|
@anton-reutov Did you renewed? 😄 |
Domain has been renewed yesterday, while it got to grace period already a second time: #2060 Even after several warnings from hestia team... |
|
...and @dpeca of course, he warned aswell... |
I don't understand the reasons for your laughter ScIT-Raphael, in every word you say, there is a negative against the project. It started with the creation of your fork |
|
@anton-reutov I'm sorry that I'm a bit negativ against the project now. But I asked you, nearly begged for a new vestacp package to fix and protect the remaining active and productive vestacp servers (#2006 (comment), #2006 (comment), #2006 (comment)). Then you were even informed from us that the vestacp domain is expiring, but nothing happened, the nameserver changed: #2006 (comment) Also you promise things, that just didnt happened and were anyway completly in the wrong direction (if you have a project with pending exploits): #2006 (comment) Just in addition, you should be also aware of another security issue with the used jquery version, which is, beside some minor ones on "high severity": https://snyk.io/test/npm/jQuery/1.7.2 So, I need to excuse myself to be "negative" against the project - but I honestly don't feel bad doing it. You arent able to patch partitialy, critical security issues within an aceptable timeframe, let thousands of servers in a instable situation and try to hold a, in my point of view, dying project "somehow" alive. I already pointed that out in your forum: https://forum.vestacp.com/viewtopic.php?f=10&t=20562#p84568 I will stay negativ about the project, until you either bring it back alive with a new patched version, inform the users about the current security issues before they install vesta or let the project die in peace. If you're not happy with that, you're free to block me from your github project and/or forum. PS: Infact you added "It started with the creation of your fork" which I missed due to writing. Hestia isnt the reason that I started thinking negativ about it - it's more the product that came out due to the situation. We all know that there were serveral security issues with the vesta infrastructure, some so bad that even digital ocean had network issues due to the amount of hacked vestacp servers which itself started to ddos. There was nearly zero communication, nothing written for weeks, users that need to find out what happened. Also deleting valid discussions in vesta forum, blaming another user in forum which even lead myself to write you in this case with a pn (never got an answer), and much other things. And aswell: It isnt "my fork", hestia started with around 5 old "vesta" members and growed massively over time - we got now more than 12k stable and secure servers. PPS: All known exploits and issues, even the jquery one have been patched in hestiacp, you're free to take the code there (leave a thanks to the hestia project if you like). It's not, as you maybe think, my target to "hurt" vesta or be negative against it - I just want that the few thousands server out there in the wild just get patched! |
|
Thank you for your reply. I understand. Only Serghey have access to compile the packages, If someone else had access there would be no such problems. Now he's waiting for me to finish adding fixes to github Againt thank you! |
|
I've sent you the link already above, you will find the rewrite here: hestiacp/hestiacp@93c2079 But this is probaly not enough, we already reworked some jquery parts in earlier commits months ago. I'm aware of the "Serghey Repo"-Problem, but why do you still try to hold the project alive when he don't want to give you access to the repo? No one can update it, Serghey clearly doesnt want to do it - probaly due to time, which I can also understand. So either he gives the access to you or you @anton-reutov need to stop the project and inform the remaining users! |
|
@anton-reutov Solved, thanks! |
Operating System (OS/VERSION):
Debian 9
VestaCP Version:
Latest version
Steps to Reproduce:
I've initialized fresh Debian 9 VPS then I've try download the installation script with:
then I get in vst-install.sh:
and I can't start installation proces
the script vst-install.sh was not downloaded correctly.
The text was updated successfully, but these errors were encountered: