Thanks Nebulon. I'll follow up with the team administering the db tomorrow. Using the nc command directly from the server running cloudron, I'm not getting an acknowledgement. So i'm hoping it's an issue at their end.
Latest posts made by markjames
-
RE: Redash connect to an external DB - Do I need to open ports?
-
RE: Redash connect to an external DB - Do I need to open ports?
While the initial request will be outgoing, the db will respond on port 1433 as well won't it?
I can probably get help to get the logs, but it's a third party who manages the db so I'd prefer to rule out the obvious before I go down that path.
So is there something I need to configure to open up 1433 for redash?
-
Redash connect to an external DB - Do I need to open ports?
Hi,
I'm currently trying to connect to a remote Sql Server DB on port 1433 (the default). I've had this port opened for my cloudron servers IP, but I still can't connect successfully.Do I need to add port 1433 in some configuration somewhere to open this port for redash/sql server?
Thanks
Mark -
RE: Installation problem during setup - AWS Cloudron AMI
Thanks, Girish,
That patch worked. I've successfully setup things.
cheers
Mark -
Installation problem during setup - AWS Cloudron AMI
Hi,
I'm trying to setup cloudron using the Cloudron AMI on AWS.
The server spins up and I'm redirected to the setupdns page as expected. However when I add my details selecting DNS provider AWS Route53 and security credentials I get and error message when I click the 'Next' button. The error is -"providerToken must be a non empty string"
Choosing alternative DNS Providers caused the same error message.
I've tried on both Firefox and Safari. Chrome doesn't allow me to advance due to the self-signed cert.
Does anyone have any suggestions?
Thanks
Mark