#selfhosting week 1, phase 3B bis: Disappointment.
Subscribed to a Ionos vps in alternative to Hostinger, but the interface is much, much more complex (I'm referring to the vps and domains management) - thought Hostinger was the worst.
But, if accessibility declaration on Hostinger says "partially accessible" giving an e-mail address (not dedicated, it's the generic support), Ionos makes me point to an Italian paragraph where they claim barrier-free then says "for support, contact us through contact form", redirecting to a German accessibility page where NO FORM is displayed. Is it this way to treat customers?
Does @fsfe and @EUCommission have something to say? These are fake accessibility declarations.
You can't say you respect all customers, when you make your showcase site mostly accessible but most important feature (the vps/firewall management panels) impossible to use. To give an example, the "edit" button for a single firewall rule is labeled as "y", the delete is "]", the add rule is "@" ... Not to say that @yunohost on Ionos creates ipv6 issues, the port TCP 25 is closed and I need to call them with EXACTLY my phone number to have them open the port for me...
I must definitely try to talk to them and start the refund procedure.
Unfortunately though, Ionos would give me 240 gb hard disk for storage while hostinger, even upgrading, would give me 100.
WTF. #accessibility #blind #frustration #selfhost #vps
Subscribed to a Ionos vps in alternative to Hostinger, but the interface is much, much more complex (I'm referring to the vps and domains management) - thought Hostinger was the worst.
But, if accessibility declaration on Hostinger says "partially accessible" giving an e-mail address (not dedicated, it's the generic support), Ionos makes me point to an Italian paragraph where they claim barrier-free then says "for support, contact us through contact form", redirecting to a German accessibility page where NO FORM is displayed. Is it this way to treat customers?
Does @fsfe and @EUCommission have something to say? These are fake accessibility declarations.
You can't say you respect all customers, when you make your showcase site mostly accessible but most important feature (the vps/firewall management panels) impossible to use. To give an example, the "edit" button for a single firewall rule is labeled as "y", the delete is "]", the add rule is "@" ... Not to say that @yunohost on Ionos creates ipv6 issues, the port TCP 25 is closed and I need to call them with EXACTLY my phone number to have them open the port for me...
I must definitely try to talk to them and start the refund procedure.
Unfortunately though, Ionos would give me 240 gb hard disk for storage while hostinger, even upgrading, would give me 100.
WTF. #accessibility #blind #frustration #selfhost #vps
André Polykanine
in reply to Elena Brescacin • • •Elena Brescacin
in reply to André Polykanine • • •Another big issue I had, was that you can assign an IPV6 address to your server, but then you must MANUALLY configure it by editing a file. /etc/network/interfaces or /etc/netplan. I found the documentation confusing and it is a very risky operation, you can unblock it through the ionos remote console, but, what about accessibility of that one?
It's like a guy telling me we're completely safe, and he has a condom in hand. A condom with braille dots on it to make it accessible. Got the idea?
Note for non-braillists: the Braille dots, in paper, are made through a pin which causes a hole on one side, the dot on the other.