ubnt CloudKey - refused connection
-
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
-
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
-
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
Edit: Except I dislike telling a client they don't have access to their own stuff. Only in instances where a client has taken something down due to lack of knowledge and inadvertently caused an outage. The issue really hasn't come up though.
-
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
It's easy to configure. I think you're making things 10x harder on yourself.
-
@travisdh1 said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
It's easy to configure. I think you're making things 10x harder on yourself.
I'll check it out.
-
@travisdh1 said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
It's easy to configure. I think you're making things 10x harder on yourself.
Aside from just web searching, do you have any particularly useful bookmarks for multiple client configs?
-
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
Edit: Except I dislike telling a client they don't have access to their own stuff. Only in instances where a client has taken something down due to lack of knowledge and inadvertently caused an outage. The issue really hasn't come up though.
It's not that they don't have access to their own stuff, they don't have access to YOUR system for managing their stuff. It's your stuff, not theirs, in this case. They can always access it in another way.
-
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
@scottalanmiller said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
Each client gets their own cloud key. If they have a bunch of servers, at $70 I can't justify each customer not having their own.
$70 seems like a lot for an inferior system. Hosted means better reliability and less effort, for less cost. Let's say you have five customers. That's $350 in non-business class hardware, or $120 / year in hosting fees. So basically three years of hosting for five customers is break even with the hardware in cost.
But with the hosting you have the ability to set up and recover easily. With the hardware, not so much. One creates a lot of expensive labour, while one does not.
I think I'd work it the other way around, even if the dongles were free, I don't think that I could normally justify the small savings versus improvements in reliability, ease of use, and reduction in labour time. Paying $70 for those caveats seems weird. If you had only one user, and they had Internet issues, and were insanely cheap (re: tight wads), then maybe. But for multiple customers?
The shorter answer is I've looked at the hosted option but honestly I just haven't explored it yet for a multi-client setup.
Do you want the customers accessing it too, so you have shared access? Or is it only for you with multiple tenants?
Most of the time (above 90%) it's just us, but there are some places that have onsite IT that might eventually. But honestly I'd say probably just us and tell them they don't have access if delegated access is a pain to configure.
You create a new user and assign that user permission to just their site. I need to redo my lab controller, but I won't get around to that till Sunday most likely. I'll try to grab some screenshots to show you, but it's just really easy.
Settings -> Admins is where to create accounts.
Edit: Except I dislike telling a client they don't have access to their own stuff. Only in instances where a client has taken something down due to lack of knowledge and inadvertently caused an outage. The issue really hasn't come up though.
That's why you have backups.
-
@bbigford said in ubnt CloudKey - refused connection:
option but honestly I just haven't explored it yet for a multi-client setup.
I have one Unifi Controller with 70 Customers and they have each their own login and can manage it from their end. This one is not hosted on Vultr but rather in AWS but it is working well.
Moving to Vultr though very soon.
-
@dbeato said in ubnt CloudKey - refused connection:
@bbigford said in ubnt CloudKey - refused connection:
option but honestly I just haven't explored it yet for a multi-client setup.
I have one Unifi Controller with 70 Customers and they have each their own login and can manage it from their end. This one is not hosted on Vultr but rather in AWS but it is working well.
Moving to Vultr though very soon.
Yeah, I've worked with a single instance managing 200+ customers. Easy, especially when you can adopt a new AP before taking it on site.
