It's true that the longer version may be a pain in the ass to type, but what is going to be easier for your clients to remember? Even with the longer domain, once someone sends you an email, their email client will likely remember the address and autocomplete. For yourself if the email is used across multiple other sites as login ID, you likely have a password manager so that'll also complete. If I were a client, it would be easier to remember the longer domain instead of the one with a non-standard TLD.

@travisdh1 said in Is Anyone Successfully Using Nextcloud Passman App For Sharing Passwords?:

I'd look at something like 1Password, and just keep the encrypted blob on your Nextcloud instance. I haven't heard of anyone having a good experience with the password manager app in Nextcloud. It's a shame, but it was not something that they were doing internally.

That's now my conclusion having tried both Passman and Passwords apps.

Looking at the app, it hasn't been updated in some time. Will see if the Passwords app is any better.

I've tested and tried to use Passman but the app seems flaky. I've never run into any problems accessing the passwords but when I share with user, they often can't access their vault even after they enter the correct decrypt password. Would love to get this working since this is perfect for sharing passwords with clients. Hoping someone here may have had better luck.

Running on Nextcloud 13.0.6 on Fedora 28.

@jaredbusch Thanks

Any benefit to doing it this way vs standard cron?

@scottalanmiller said in Sangoma Linux and mondo archive:

@nashbrydges said in Sangoma Linux and mondo archive:

@dustinb3403 said in Sangoma Linux and mondo archive:

@nashbrydges use any solution that works for your provider or hypervisor.

Thanks, yeah that makes obvious sense, but the question is related to on-premises physical box FreePBX installs. I have a couple clients with Sangoma FreePBX appliances (no HA) so it's for these specific use-cases that I was asking about.

Honestly, and I have clients who've done this, the first thing we do is get them off of the physical boxes. If it's important enough to want to run, it's important enough to run well. The physical boxes just make everything more fragile and difficult, especially when it comes to backups and restores. While I understand some people might deploy this way, we always approach this as "fix it" rather than "live with it".

Again, no argument from me on this.

@dustinb3403 said in Sangoma Linux and mondo archive:

@nashbrydges said in Sangoma Linux and mondo archive:

@dustinb3403 said in Sangoma Linux and mondo archive:

@nashbrydges use any solution that works for your provider or hypervisor.

Thanks, yeah that makes obvious sense, but the question is related to on-premises physical box FreePBX installs. I have a couple clients with Sangoma FreePBX appliances (no HA) so it's for these specific use-cases that I was asking about.

As previously discussed, your phone system shouldn't be physically installed... As it's usually critically important.

I think we all agree on this one. You won't get any argument from me. Only clients that have physical installs are those where I've taken over from another support group.

@dustinb3403 said in Sangoma Linux and mondo archive:

@nashbrydges use any solution that works for your provider or hypervisor.

Thanks, yeah that makes obvious sense, but the question is related to on-premises physical box FreePBX installs. I have a couple clients with Sangoma FreePBX appliances (no HA) so it's for these specific use-cases that I was asking about.

@jaredbusch said in Sangoma Linux and mondo archive:

@scottalanmiller said in Sangoma Linux and mondo archive:

Also, FreePBX has built in backup utility for the application. There is no need to back up the Linux OS. You can, but it's not necessary or particularly useful. Just restore the OS, and restore the settings.

It sucks though. Had tons of issues with it over the years.

That is actually the big feature of FreePBX 15 (just now in Alpha testing).

What's your preferred choice for FreePBX backups? If you're running on Vultr or other VPS I assume you're using their backup options but for anyone running an on-premises physical box, what's your recommendation? Has anyone ever used something like Veeam Agent for Linux? Is that even a viable option?

I've not had to recover a FreePBX setup from backup so learning that it sucks means I should probably look at other options for clients.