Posts made by krzykat

@scottalanmiller

My reason for asking is kids school units and wanting to have controls. I just installed circle for the house - great for controlling online time for kids. Would be great if I could convert a win laptop to a chromebook that allowed the installation of the android circle app so that I could monitor more closely what they are doing on their computers. Free allows me to see how much time they spend on each app as well as their browsing history.

Has anyone ever turned a Win Laptop into Chrome? https://www.androidpolice.com/2020/06/13/how-to-turn-your-old-slow-laptop-into-a-sleek-chromebook/

@JasGot What are you referencing? The DIP at Skyetel or ?

@JaredBusch

Nevermind - never knew that was an option

@JaredBusch

How did you do a screen capture of the phone's display?

This sounds like a complicated answer, but so is your problem. ... What if you setup 2 tenants - Tenant 1 = client, Tenant 2 = overflow - then limit the first tenant (your client) with trunk Skyetel to the 4 trunk limit. Then on Skyetel, you setup failover Tenant1 -> Tenant2. Then Tenant 2 will grab the extra calls destined to voicemail. Then you setup a trunk betweeen those two without the 4 trunk limit, and that trunk on Tenant 1 goes immediately to voicemail.

@syko24 Almost sounds like a SIP-ALG issue to me. Make sure SIP-ALG is disabled on your router. I've got a 2170 laying around if it can help.

I really like Synology or if you want to do it yourself with existing hardware, fire up Xpenology - works great.

@JasGot They want customer's IT team to do it so that they will be on the hook next time instead of Comcast. I think I'd get in writing from them that international is turned off from their side, so that if/when it happens again, you can pull out that document and shove it down their throat.

@scottalanmiller

I think you need to have mitigation plans for key man not just for the longevity of your company and your heirs, but I've been asked more than a couple of times if we have plans in effect in case God forbid, that I catch this and fall over. Yes - its very important for employees and clients that you have a proper succession plan in place and I've had some conversations about that already in light of what all is going on. Then realized, I should have done this long ago ... what happens if I get hit by a car crossing the road ... things need to proceed and a plan needs to be in place.

@Kyle
We're doing Synology with VPN

@JasGot

Have you checked your LE credentials to see that its working properly?

@JasGot

I haven't looked at their install script in a while, but for sure there was a LE issue. Here's a copy of my note to Skyetel regarding the issue. I thought the script had been updated with our patch, but here it is in case not:

FYI - we've resolved the issue, and I can only assume anyone else that has installed Postcards should have the same issue.

The problem is indeed an issue with Let's Encrypt, and specifically:

docker: jrcs/letsencrypt-nginx-proxy-companion

To fix this issue, please update the docker-compose.override.yml file during builds.

Row 35 should read: image: jrcs/letsencrypt-nginx-proxy-companion:latest

This will insure that the current version for the let's encrypt proxy is called and eliminate the issue.

Anyone know how I can have a device accessible by more than one user or group?

Group1
Computer A
Computer B
Computer C
Group2
Computer D

I've got user Adam with access to Group1 - and things are fine, but then what if I want to have user Brad access only to Computer A ??

@Skyetel

FYI: - I AM running with Centos 7 - successfully - and you are now addressing several of our concerns.

One thing we really want to see in the new version that I don't see listed is the option to have user .. then if user1 replies to one message and user2 replies to the next... we know who did what.

@JaredBusch

There is a current issue with the SSL let's encrypt that I just submitted to them to resolve (they are using an outdated version with Acme 1 instead of the newer Acme 2):

FYI - we've resolved the issue, and I can only assume anyone else that has installed Postcards should have the same issue.

The problem is indeed an issue with Let's Encrypt, and specifically:

docker: jrcs/letsencrypt-nginx-proxy-companion

To fix this issue, please update the docker-compose.override.yml file during builds.

Row 35 should read: image: jrcs/letsencrypt-nginx-proxy-companion:latest

This will insure that the current version for the let's encrypt proxy is called and eliminate the issue.