Search results

Chhers bud all sorted now didnt realise how easy it was to setup

The SSH Key Was the way i went. Im not a linux person so didnt know about this but by god it was easy to setup.

Cut a long story short I think I have over provisioned the Channels on my shared sip trunk. Currently have a number of customers on a shared trunk with X amount of Channels. So basically its first come first served. I dont imagine that the maximum number of calls at ayone time actaully...

Oh well looks like I had something wrong with the script I was using to restore i had the line pg_restore -Fc --host=127.0.0.1 --dbname=fusionpbx --username=fusionpbx /var/backups/fusionpbx/postgresql/fusionpbx$ Searched through the forums again and found pg_restore -Fc --host=127.0.0.1...

Fresh in stall of Fusion on Debian 9. Ran a restore and it ended with: pg_restore: error: could not open input file "/var/backups/fusionpbx/postgresql/fusionpbx$": No such file or directory Restore Complete So checked if the files where there: root@pbx:~# cd /var/backups/fusionpbx/postgresql...

Hi I have added the follwing line to Crontab but unsure if it working (Does not see to be) I take it I may have the syntax wrong # m h dom mon dow command 0 3 * * * /root/restore.sh | mail -s "PBX Restore Complete" technical@xxxxxxxxx.co.uk I dont get an email and it does not look like...

Thanks you pointed me in the right direction. Seems under /etc/nginx/sites-available/ I looked at the FusionPBX file and within this were the typos altered that and reran the ./letsencrypt.sh and it worked fine this time.. thank you both Bifur and Adrian for their help.

Some slight progress but still got an error in the end nginx: [emerg] BIO_new_file("/etc/dehydrated/certs/oip.XXXXXX-it.co.uk/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/dehydrated/certs/oip.XXXXXXXX-it.co.uk/fullchain.pem','r')...

been waiting around 20 minutes and tried again last night actuaklky left it over night untill this morning and got the same error.

Sorry didnt have my glasses on lol Hooks script : #!/usr/bin/env bash # based on https://github.com/lukas2511/dehydrated/wiki/example-dns-01-nsupdate-script set -e set -u set -o pipefail case "$1" in "deploy_challenge") echo "" echo "Add the following to the zone...

Im updating the DNS through the Control panle for the domain then testing it via MXtoolbox to see if its updated.

Config file looks like this ######################################################## # This is the main config file for dehydrated # # # # This file is looked for in the following locations: # # $SCRIPTDIR/config (next to this...

Keep getting this: + Responding to challenge for voip.xxxxxx-it.co.uk authorization... Unknown hook "invalid_challenge" + Cleaning challenge tokens... Now you can remove the following from the zone definition of voip.xxxxxxx-it.co.uk: _acme-challenge.voip.xxxxxxx-it.co.uk. IN TXT...

Did you ever resolve this issue I'm having the same errors.

Turns out it was the Mail server playing up.

Im trying to setup the emails settings on a fresh install and seem to be having an issue in that even if I chnge the details under default settings they donet seem to be updating. When I send a test email its using the original details I entered in the settings. Also Im unable to send any test...

I had already tried it once which said it had suceeded but the Cert is still showwing as Localhost. So i treid it again as if I was renewing it. and thats the error i got

new install nad trying to setup leysencrypt but getting this: root@voip:/usr/src/fusionpbx-install.sh/debian/resources# ./letsencrypt.sh Domain Name: *.voip.xxxxxxxx.co.uk Email Address: andrew@sxxxxxxx.co.uk fatal: destination path 'dehydrated' already exists and is not an empty directory...

Look slike I better get some reading done :)

Hi I have thsi script (Copied from this forum) When I run it to test on a new install it keeps asking for the rooot password. How do I avoid this either tell the script where the password is or tell it what it is. So that I can run this as a daily cron at night. #!/bin/sh now=$(date...