Error: Parsing error when changing IP Address
Error: Parsing error when changing IP Address
Hey I've seen this question in the forums before but no answers...
My server is on amazon aws linux. When I stopped the instance and started again I was assigned a new ip address.
Then I went to vestacp and changed the ip address under:
- eth0---> new IP
- Dns ---> new IP
The site is opening fine with the new ip.
BUT
Under Web Section in vesta I still see the old IP address under the domain name. But when I click edit I see the new ip address but can't save anything I get Error: Parsing error
Any advise?
thanks
My server is on amazon aws linux. When I stopped the instance and started again I was assigned a new ip address.
Then I went to vestacp and changed the ip address under:
- eth0---> new IP
- Dns ---> new IP
The site is opening fine with the new ip.
BUT
Under Web Section in vesta I still see the old IP address under the domain name. But when I click edit I see the new ip address but can't save anything I get Error: Parsing error
Any advise?
thanks
-
- Posts: 2
- Joined: Thu Aug 13, 2015 11:18 am
Re: Error: Parsing error when changing IP Address
Here is a workaround solution:
Edit the file /usr/local/vesta/users/<user>/web.conf so that the IP addresses in the file match your server's updated IP address. Replace <user> with the name of the user owning the domains you need to update.
If you are not sure, here is a failproof scenario:
1. Log into Vesta as the user owning the domain(s) you have an error with.
2. Add a new "junk" domain, e.g. example.com.
3. Edit the file /usr/local/vesta/users/<user>/web.conf, where <user> is the name of the login user used in 1 above.
4. Copy the IP in the "example.com" line to the domains you are having errors with (or to all of them).
5. Return to Vesta and remove the "junk" domain.
6. Enjoy.
Edit the file /usr/local/vesta/users/<user>/web.conf so that the IP addresses in the file match your server's updated IP address. Replace <user> with the name of the user owning the domains you need to update.
If you are not sure, here is a failproof scenario:
1. Log into Vesta as the user owning the domain(s) you have an error with.
2. Add a new "junk" domain, e.g. example.com.
3. Edit the file /usr/local/vesta/users/<user>/web.conf, where <user> is the name of the login user used in 1 above.
4. Copy the IP in the "example.com" line to the domains you are having errors with (or to all of them).
5. Return to Vesta and remove the "junk" domain.
6. Enjoy.