I have the main page, and cPanel secured with SSL, but when a user signs up the security image does not load due to mixed secure content, http://order.<? echo "$yourdomain" ;?>/image.php?id=<?PHP echo $id; ?>   How would I go about securing the order. subdomain of my free host website?. It also displays a security warning when visiting the order. subdomain. And when changing the image to use https, it doesn't display

While I'm not directly taking part in the work myself, I am actively communicating with the team regarding your feedback.

I have to ask, are you actually going to work with iFN to make the changes we suggest, or are you just asking to ask?

you can’t unsee it

Thought you meant premium (cPanel) reseller plans.    1. What do you like the most about ByetHost? Its free, and actually provides pretty good resources  2. What don’t you like about ByetHost? API is a little limiting (Having support to add/remove domain and databases would be nice) 3. If you could change one thing about ByetHost, what would it be? The API 4. What’s one thing you wouldn’t want to change about ByetHost? Pricing, current limits & ease of use 5. How easy was it for you to set up your website on ByetHost? Not very easy. The default experience is really bad from a UI/UX perspective, and even from a brand perspective. Took quite a bit of time (I think 2 years) to get a working client area setup.  6. Have you ever considered upgrading to iFastNet's premium hosting? Why or why not? I have considered it, but have ultimately decided not to. There are no features that I am aware of that make it better than other hosts, and the support experience I’ve had as a reseller could be improved upon. I’m also not a fan of WHMCS (especially vanilla installs) and try to avoid it.  7. Do you use the Byet.net forum for support and community? I think this question is a bit biased since it’s on the forum, but yes.  8. Any other suggestions or feedback? Improving the API is the major suggestion I have (And I would be happy to help do so).    Another is improving the suspension experience. It would be nice to be able to customize the suspension page (Even if linking to iFN is a requirement, that’s fine), and have better organization of how the callbacks are sent (there is no consistency, and stuff seems missing. Introducing a v2 callback would be nice. Again, happy to help). Being able to have more control over what accounts are suspended / unsuspended (Like being able to communicate SPAM_COMPLAINT or PHISHING over the API so if the user creates a support ticket staff know not to reactivate it.