Community

Hello Ceyarrecks,

Thank you for your message.

after tinkering, I find that the Cloud Flare anti-porn/malware DNS (1.1.1.3 / 1.0.0.3) is blocking "id.remoteutilities.com."
switching to default Cloud Flare DNS (1.1.1.1 / 1.0.0.1) does NOT have such limitation.

Thank you for bringing this to our attention. We've recently received a report on the same issue from another user here.
We've already contacted CloudFlare and requested them to whitelist id.remoteutilities.com which is our public ID servers' DNS name that is used for Internet-ID connections and reported the issue to our development department as well. Hopefully, this would be resolved soon.

It would be very helpful if you could contact CloudFlare as well, as their customer, and report on the issue. We believe they would take reports from their customers into consideration much faster.

would setting up one's own RU Server allow one to retain the above protections while allowing unrestricted Remote Utilities?
would there be any caveats?

Yes, in case if you set up your own self-hosted RU Server, then this makes you independent from our company's servers when you use an Internet-ID connection. There are absolutely no limitations/restrictions on using RU Server, on the opposite, this would bring immediate gains in speed and performance for Internet-ID connection. In addition, using RU Server allows you to use synchronization and authorization roles that are only available with the self-hosted server. For more information on the RU Server and its benefits please see this page.

Please let us know if you have more questions.

Hello Ceyarrecks ,

Thank you for your message.

The origin web server for remoteutilities.com is responding slowly to initial requests for uncached HTML content.

The "origin web server" of remote utilities (remoteutilities.com) is hosted at Digital Ocean and has nothing to do with the ID service. The subdomain id.remoteutilities.com points at our Internet-ID service which is not a web server.

I'm afraid CloudFlare's diagnostics tool only considers all services on the web to be html/www which is apparently not the case.

Still, we will investigate the issue further and let you know. Thank you for your patience.

Hello Ceyarrecks,

Thank you for the update.

I think it's safe to ignore these emails given that you've already submitted the issue via this form. We've also reported the issue to the CloudFlare support service and submitted the required information. We're currently expecting an update on this from them, but also receive similar automatic notifications sometimes. We will let you know as soon as we receive any updates on the issue from the CloudFlare support team. Sorry for the inconvenience.

Please let us know if you have more questions.

Hello Ceyarrecks,

Thank you for providing us your ticket number for a reference. We've contacted the Cloudflare support team once again and referred to your ticket as well. Hopefully, they will provide an update on the issue soon. I'll get back to you as soon as we receive an update from their support team.

Thank you!