myVesta

A little update. I tested to remove the domain, remove the account and add everything again without putting the website content back, it still throws errors so it has to be something inside MyVesta, as it only happens on IDN-domain names. I get this in the logfile [proxy_fcgi:error] [pid 3865343:tid...

I have a few IDN-domainnames, which contains special chars. The domain starts with xn-- If i input the xn-- domain into vesta, it does not work. If i input the domain as its written normally, i can add SSL and everything. But when trying to reach it online, i get "file not found" no matter...

I have alot of different Myvesta-installs, sometimes i need to move between machines.

A suggestion for future functions.
Make the v-clone-website command able to clone between servers.

We will release a script next month or possibly within two months, which will enable fast and easy migration of one myVesta server to another. This script will have all the necessary options integrated, making it highly useful for situations where you need to quickly and easly scale your server/har...

I like this option!
Sometimes i do something stupid and pulls down the machine and its perfect with a paid solution to solve the issues

While waiting if someone had a smart suggestion, i was looking around myself. I checked out all V-CLI-commands without luck, i might have missed one that makes this change? The "v-normalize-restored-user" was a option, but i found it too late 🤣 So what i did. - I decompressed the dns-folde...

No thats not a issue, its a DNS-clustered machine. I will empty NS2 and re-sync it with the new main machine later (ns1). Both of them will be online while the dns-data changes. like this Old server has ip: 111.111.111.111 (this is ns1, master) New server has ip: 222.222.222.222 (this will be ns1, n...

The basics with installing the new setup and importing the backups are clear and no problem. The issue is with alot of domains pointing to the IP of the old machine, i am looking for a solution so i can do a bulk edit of everything. Technically i can just do a "sed -i" and replace the IP o...

Nice, that might explain the issue

Edit: changed now on all five servers with issues, and they all report normal function in syslog on bind.

Thank you for correcting my stupidity, i should have known

After some reading on the SRV record, i think this is a bug in MyVesta ? (and vesta too, i remember having this since long time ago) In my first post i found out that all domains with issues had a SRV-record. I tried adding a test domain, named testdomain.com Everything looked nice. Then i added thi...