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.
Blank DNS tab on web interface
Blank DNS tab on web interface
Hi ,
I have a completely working veta cp ( well.. except for the issue below). My domains are working, websites and all DNS records I previously setup are working. But non of the DNS records show up in the web admin panel. This is happening for all user accounts on the host. All other tabs, web, mail, db etc get populated normally. The DNS tab always shows 0 domains. That being said, all the dns records come up when I do a v-list-dns-records for any user and any domain.
Can someone please point me in the right direction to resolve this issue?
With regards,
JC
Edit:
I'm running debian 8
I have already tried the symlink solution (ln -s /proc/self/fd /dev/fd .) but debian says the target already exists.
my nginx-error.log file does not contain any errors around the time I try to make the web call.
I have a completely working veta cp ( well.. except for the issue below). My domains are working, websites and all DNS records I previously setup are working. But non of the DNS records show up in the web admin panel. This is happening for all user accounts on the host. All other tabs, web, mail, db etc get populated normally. The DNS tab always shows 0 domains. That being said, all the dns records come up when I do a v-list-dns-records for any user and any domain.
Can someone please point me in the right direction to resolve this issue?
With regards,
JC
Edit:
I'm running debian 8
I have already tried the symlink solution (ln -s /proc/self/fd /dev/fd .) but debian says the target already exists.
my nginx-error.log file does not contain any errors around the time I try to make the web call.
Re: Blank DNS tab on web interface
Managed to sort it out our self. We replaced v-list-dns-domains script from the install package. This seems to have resolved the issue. I believe, it might have got corrupted during some of our API extension tests. Nothing wrong with the CP :) .