We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Is This VestaCP's Longtime BUG???
Is This VestaCP's Longtime BUG???
everyone please check all your domain hosted on vestacp try add '/css/bootstrap.min.css' after your domain name in your browser, for example:
example.com/css/bootstrap.min.css
it shows there's a 'bootstrap.min.css' in your server even tho i dont have any file yet in under that domain name, I try it using fresh install combination of:
nginx+apache on centos (DO)
apache on centos (OVH)
all of above configuration showing this weird action. I found this bug when I'm seeing my 'css/bootstrap.min.css' is always showing v3.1.1 even tho i upgraded it to v3.3.1
Then I try to delete the file. That weird file still shows up. I try moving my domain out from cloudflare. still same. i try clean install vestacp without any file added. it still magically shows up. even on clean DO instances. WTH is this file?
Because of this file I cant update my bootstrap.min.css without moving it to another folder (it only affectwhen you put it in /css/ folder)
Can someone explain this?
example.com/css/bootstrap.min.css
it shows there's a 'bootstrap.min.css' in your server even tho i dont have any file yet in under that domain name, I try it using fresh install combination of:
nginx+apache on centos (DO)
apache on centos (OVH)
all of above configuration showing this weird action. I found this bug when I'm seeing my 'css/bootstrap.min.css' is always showing v3.1.1 even tho i upgraded it to v3.3.1
Then I try to delete the file. That weird file still shows up. I try moving my domain out from cloudflare. still same. i try clean install vestacp without any file added. it still magically shows up. even on clean DO instances. WTH is this file?
Because of this file I cant update my bootstrap.min.css without moving it to another folder (it only affectwhen you put it in /css/ folder)
Can someone explain this?
-
- Support team
- Posts: 1111
- Joined: Tue Jul 30, 2013 10:18 pm
- Contact:
- Os: CentOS 6x
- Web: nginx + php-fpm
Re: Is This VestaCP's Longtime BUG???
For mydomain.com/css/bootstrap.min.css I see 404 Not Found only.
Re: Is This VestaCP's Longtime BUG???
Hi grayfolk, do you use any of this configuratation:
nginx+apache on centos
apache on centos
And im using basic vestacp install command:
curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh
nginx+apache on centos
apache on centos
And im using basic vestacp install command:
curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh
-
- Support team
- Posts: 1111
- Joined: Tue Jul 30, 2013 10:18 pm
- Contact:
- Os: CentOS 6x
- Web: nginx + php-fpm
Re: Is This VestaCP's Longtime BUG???
Hi. Same configuration, same installation process.
Re: Is This VestaCP's Longtime BUG???
its doesnt make any sense. but anyway I found the problem, all the files here "\usr\share\httpd\noindex" is accessible thru all the domains. Its apache welcome page directory. How to disable this?
grayfolk do you have any files inside "\usr\share\httpd\noindex"? because vestacp default installation will have that files in that folder as well. so i'm 100% sure it will affect all vestacp installation which using apache server.
grayfolk do you have any files inside "\usr\share\httpd\noindex"? because vestacp default installation will have that files in that folder as well. so i'm 100% sure it will affect all vestacp installation which using apache server.
-
- Support team
- Posts: 1111
- Joined: Tue Jul 30, 2013 10:18 pm
- Contact:
- Os: CentOS 6x
- Web: nginx + php-fpm
Re: Is This VestaCP's Longtime BUG???
First, i dont have \usr\share\httpd folder.
Second, please, check nginx/httpd configs and found where this folder pointed to your sites.
Really, i think this is just your bug, not a Vesta.
P.S. Can you give me access to server with this issue?
Second, please, check nginx/httpd configs and found where this folder pointed to your sites.
Really, i think this is just your bug, not a Vesta.
P.S. Can you give me access to server with this issue?
Re: Is This VestaCP's Longtime BUG???
Gray, Do you have OVH/DO/VULTR?
Here's the installation steps:
-) deploy new server instance with centos 7
-) login to ssh
-) enter this command:
curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh
-) answer 'y' to the first question (default installation)
-) after the installation is finished say "abracadabra" (this is the most important part)
now check "\usr\share\httpd\noindex\" folder
Here's the prove (i done it with 2 different server, DO and VULTR):
https://www.photobox.co.uk/my/photo?alb ... 1650786426
I can do this 100x in a row without any single fail. let me said once again its 100% will affect anyone who use default installation configuration. :)
Here's the installation steps:
-) deploy new server instance with centos 7
-) login to ssh
-) enter this command:
curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh
-) answer 'y' to the first question (default installation)
-) after the installation is finished say "abracadabra" (this is the most important part)
now check "\usr\share\httpd\noindex\" folder
Here's the prove (i done it with 2 different server, DO and VULTR):
https://www.photobox.co.uk/my/photo?alb ... 1650786426
I can do this 100x in a row without any single fail. let me said once again its 100% will affect anyone who use default installation configuration. :)