Paul

In order to sell a dedicated IP, you need to create a configurable option for it. Packages > Options. Take a look at the doc page I linked, hopefully that makes sense. (Here https://docs.blesta.com/display/user/Multicraft?preview=/3833872/3899409/3.png#Multicraft-CreatingaConfigurableOption) So, I don't think it's even trying to use a dedicated IP. It's trying to use a shared IP, and that is not configured properly on your Multicraft master server. See https://docs.blesta.com/display/user/Multicraft#Multicraft-SettingtheServerIP on how to set that.

Does it assign the correct IP if you don't use a dedicated IP (Or does it use 0.0.0.0 also)? Did you configure multicraft per https://docs.blesta.com/display/user/Multicraft#Multicraft-SettingtheServerIP ? What does this screen look like to you? https://docs.blesta.com/display/user/Multicraft?preview=/3833872/3899409/3.png#Multicraft-CreatingaConfigurableOption (Not including Basic Settings, just Dedicated IP Addresses?) Also, are you using a config option dedicated_ip for dedicated IPS per the docs (Under Configurable Options Overview)

I think Timothy is probably right. Do you have available/unused dedicated IPs in your WHM/cPanel server?

We ran into more PHP 7 issues and are currently working through them.

https://clients.cyandark.com loads fine for me, but I am IPv4 only. If you have IPv6, it will try to connect via IPv6 because there is an AAAA record. So, if the server is not configured to use IPv6, then the AAAA record should be deleted and that would probably solve it.

If no IPv6 on the server, there shouldn't be an AAAA record on the DNS zone.

What do you mean by "global custom field"? Can you elaborate?

It would be a good idea to create the request anyway, you can link to the task ID in Jira and the thread, and we can update the status to accepted. Will help us to prioritize because people can up vote.

Check the gateway log to be sure. Tools > Logs > Gateway, click the row to expand and show the raw input/output. If it's not settled, void is what you want to use, so that definitely could be it.

Thank you very much for the kind words.

Looks great, nice work!

I reset your password and PM'd it to you, let me know if you have any trouble logging in.

He sent me a PM this morning. Let's tag him @cyandark

We are trying out a new application for better handling of Feature Requests. Please register at https://requests.blesta.com The system allows for better tracking of feature requests, and allows users to up vote them. It should allow us to better prioritize requests. Please create an account there and give it a try!

What's the deal with v2? Ha. v2 actually has a lot of my code in it, sounds scary in hindsight.

Sign up with EVO through our partnership, get a good rate, and use Authorize.net https://www.blesta.com/partners/

Oh yeah! Does the debugger work on v4?

Ah, that makes sense. That's a relief. What debugger are you using?

That's my recommendation yes.

What module are you using, is it SolusVM?

I think so, but I don't recommend it. Having a history of when and from where customers log in can be useful in audits. Yes, but there are some logs that are not rotated intentionally, like the mail log and user logins. The mail log has the tendency to get the largest, but has a complete history of all email each customer received, which can be very useful. Only the retention policy (number of days to keep logs), as Mike mentioned earlier in this thread.

Whatever you do, never delete your cron log. The rotation policy will handle that in a safe way, deleting it manually will cause problems. Some logs are not rotated as part of this policy, like the mail log. The mail log is safe to truncate manually. I don't recommend truncating any other logs. Storage is cheap and unless you have tens of thousands of customers, your database should remain manageable.

That is our recommendation. Email addresses used by the support system shouldn't be used to sign up at other websites, or respond externally to customers or potential customers. Addresses used by the support system, should be used exclusively by the support system.

Interesting. So, Plesk expects the IP address? It would explain why we implemented it this way to begin with.

Is it April Fools in the UK today?