Vesta Control Panel - Forum

I cannot make any change to my website's settings because it always throws "error: parsing error" in the control panel whenever I try to change my Apache package to phpcgi or anything else. All I want to do is enable PHP so I can use my MySQL databse. This is a persistent issue.

I am having similar issues. My ISP recently assigned us a new static IP address. I was able to update it in most places, except in the Web portion. Trying to do so result in a "Parsing Error" error message. How can I make changes to the setting of the web site?

I am also having the exact same issue. Recently got a new external IP and can't change it in the web portion without deleting and re-adding the domain, which I don't want to do.

Yeah, I've also had this issue when trying to change the system IP. I have submitted a bug report already on the github project page.

I've again hit this problem and have no fix. Any updates or workarounds???

I'm having the same exact error after my ISP gave me a new IP address. Please let me know if anyone needs any information.

Thanks!

I have been seeing this error as well. Not only does it prevent changing the IP address of the main server and my first domain, but it also prevents changing packages, adding a FTP users, and a slew of other issues.

Here is the error.log

2015-03-25 10:31:39 v-change-web-domain-ip **** virginiaseo.org 96.89.31.*** no [Error 12]
2015-03-25 10:37:15 v-change-web-domain-ip **** server4.thedilldesign.com 96.89.31.*** no [Error 12]

To further update, when I try to change one of my affected domain IP using the script directly here is the output:

[root@server4 bin]# v-change-web-domain-ip username virginiaseo.org 96.89.31.***
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
sed: -e expression #1, char 0: no previous regular expression
Error: Parsing error
[root@server4 bin]#

In your(s) admin panel IP - first check
Then assign domain to new IP - second move

Sorry, but that does not work, there is a bug I think. Those are the steps which I followed when I changed IP addresses. The problem is that from the main control pane screen under Web my domain has the old IP listed. When I click Edit, the dropdown box only has my new IP listed, the old one is not even there. Now when I save this page is when I get the parsing error, which does not let me save anything.

What I just now had to do to fix it was delete the web domain and re add it again, which gave it the new IP. The old IP that it was stuck on did not exist anywhere else on the server, besides in the control panel for that web domain. All DNS and the main server IP had already been adjusted.

Now that this web domain has been added back under the new IP, all of my parse errors are gone- I can change packages and add FTP users again which is great.

As a workaround to those of you with the problem still, do this:

Take a backup! I recommend doing this from your control panel, and then going in via FTP/SSH and downloading the backup. I did it via CLI- In my case my user was virginiaseo, so I logged in via SSH with root and did this:
I then backed up my conf and web directories manually:
Now log into your control panel and log in as user by going to Users > and clicking Log In as XXXX next to the user- in my case it was virginiaseo. Now go to web, and next to the domain giving you a problem, click delete. At this point you will get a parse error, but the domain will be gone.

No click new domain, and create it with the same domain name. Add in your SSL code if you were on SSL. now move those directories back to where they were: And restart your services:
This operation does not affect your DNS and Mail, bu you should go through everything and make sure no settings are jacked up.

Here is the bug page on this issue: https://github.com/serghey-rodin/vesta/issues/230
Here is a script which helps to change the IP of the server, which I used at one point. This script when used will lead to the problem in this thread for your shared IP in some circumstances- out of my 10 domains on this server, the only domains that gave me trouble were my first domain, and my hostname domain which I created for mail/logging purposes. viewtopic.php?f=10&t=5975

In the future, it might be easier to stand up a new Vesta instance on the new IP and then just migrate everything over instead of changing the IP.