Can't see current, or add new web domains from Vesta

[jtothez]

I've run Vesta across many different servers and have never run into this. I added a new domain yesterday from the Vesta CP, which then broke the Apache/nginx setup and caused my other sites hosted on this server to go down. To fix, I manually went into the Apache and nginx config's and removed the new domain Vesta had created.

This got my current sites working again, but I still cannot see my current domains in Vesta CP, nor can I add a new web domain (I actually get a 505 error when I try to add the new web domain from within Vesta)

Anyone run into this? I've been looking at the logs, but I'm not sure I'm seeing anything useful.

[jtothez]

Screenshot for reference:

[mehargags]

just select the user and "rebuild web" for him... it should fix it.
beware... it may remove any custom config you may have done in nginx/apache2 config for the sites (if any)

[jtothez]

Thanks for the reply. Just tried rebuilding - still shows blank.

I should also note that I fixed the 505 errors for adding domains by fixing some permissions - so that is no longer an issue but the control panel still is blank when trying to view the domains.

Interesting that running v-list-web-domains admin shows the domain I had added, but if I try to remove it with v-delete-web-domain it says it does not exist. Also tried removing it with tailing spaces thinking maybe I fat fingered typing the domain when creating it in Vesta but still says it doesn't exist.

What config file does that command grab the domains from? Wonder if it's just a matter of cleaning it up manually...

[mehargags]

I'm not sure about which file it reads for domain records but I remember this behaviour has been reported before, probably after the v16 update was issued.

Can you check the vesta web ui in a new browser... in incognito mode ? or probably a different PC altogether to make sure we are not seeing cached artifacts ?

If you wish...you may PM me your server credentials... both SSH and VestaCP, I'll be happy to investigate!!

[mehargags]

I checked it thoroughly...

There was one such incident reported earlier viewtopic.php?f=41&t=11874&p=46178&hili ... ins#p46178

I did

Code: Select all

ln -s /proc/self/fd /dev/fd

but it still doesn't help

VestaCP shows all DBs/ DNS etc... just doesn't show any web domains only for user admin

Made a new user, created domains, shows perfect all domains for this new user

Even updated v-list-web-domain and v-list-web-domains from GitHub
Still doesn't help

I think you should PM Imperio so he can check your server... may be something ubuntu specific bug

Sorry... for not being able to resolve your issue

[jtothez]

Thanks again Mehargags!

Anyone else able to take a stab at this? I PM'd Imperio but haven't heard back - I'm still stumped on it myself and am just hoping it will be resolved in a future release....

[juslintek]

Same problem over here after

Code: Select all

sed -i 's/socket/default/' /usr/local/vesta/data/users/admin/web.conf

Code: Select all

v-list-web-domains admin

works, so I have no idea whats wrong. Guess need to dive into vestas php to see whats wrong. Recently had problem with letsencrypt and all websites crashed, died and wow that was a disaster, for some reason curl started resolving ipv6, which was down. So I had to add to all curl in all script -4 param to use ipv4.

This vesta is so unreliable its like basement cpanel project. I myself am working in hosting company as developer. And developed few custom panels for our shared hosting, so I see a lot of improvement is required. :-)

So after I find the file responsible for outputing list of web-domains I'll try to var_dump its exec, because I think its using exec to get list of web-domains from

Code: Select all

v-list-web-domains

. Guess array is broken for iteration or hash check is not passing will let you know...

UPDATED:

My problem was that I haven't left empty line at the end. So json_decode wasn't able to parse properly json, because v-list-web-domains command wasn't adding because of that before last json element comma.