No.
But i know Sysadmins that use Fortigate and has no problems.
As its a new domain i guess its not updated the rules. Can you access www.bamfordsrepairs.co.uk ?
Yes, I can access: https://www.bamfordsrepairs.co.uk/
Then they are not using the web filtering to blocking phishing sites:
1 Like
No sure then.
Well the problem here is solved anyway.
2 Likes
Pretty sure that would call for a new topic to resolve, but it may be out of scope here. A definite curiosity though.
Yeah most like the Phishing List that is not updated.
Cheers for your help guys i am all up and running here 
Can be marked as solved 
1 Like
Only you can click to mark solved.
Glad to hear all up and running
1 Like
You hold the power to do that, my friend. 
1 Like
off-topic, but are you a moderator?
I saw something about that in the lounge.
I hope I didn't just out you.
1 Like
Really i thought you had to be a mod for that?
to mark this as solved?
1 Like
Whomever opens the topic has that power - just find a post you think solved the problem and mark it as the "solution"
1 Like
Wish multiple solutions could be marked. There really wasn't a single-post solution. Something to bring up to the elders, perhaps?
As long as there is a marked solution, people will read through to find and understand
2 Likes
Yes i agree maybe that is something for the team who manages the site.
I have marked the post as solved. I mean the title of the post.
2 Likes
Hi guys,
Just a quick update. Everything seems to be working great here but i do have three more questions tho,
If i wanted to add another domain to the Cert on the Mail Server im guessing i need to re-run the same command as before? Lets say i need to add domain 3,
certbot certonly --cert-name mailcert --dns-digitalocean --dns-digitalocean-credentials ~/.secrets/certbot/digitalocean.ini --dns-digitalocean-propagation-seconds 60 --post-hook "service postfix reload; service dovecot reload;" -d mail.domain1.com,mail.domain2.com,mail.domain3.com
Now lets say i need to remove domain3.com is this correct?
certbot certonly --cert-name mailcert --dns-digitalocean --dns-digitalocean-credentials ~/.secrets/certbot/digitalocean.ini --dns-digitalocean-propagation-seconds 60 --post-hook "service postfix reload; service dovecot reload;" -d mail.domain1.com,mail.domain2.com
Question 3, How do i know the Cert has been updated?
Just asking for the future so i know and can add it to my notes.
Thanks.
Jack.
1 Like
The first two answers are free:
A1. That seems correct.
A2. That seems like it needs another action word... [verb] to induce the reduction without a complaint.
And the third answer is on-the-house!:
A3. certbot certificates will always show all there needs to know about all your certs [try it now]
Maybe @griffin has the correct verbiage to properly complete A2.
1 Like
To add to what @rg305 has correctly indicated:
For adding and removing domain names, you have exactly the right idea.
Straight from the horse's mouth...
Consider using
--cert-nameinstead of--expand, as it gives more control over which certificate is modified and it lets you remove domains as well as adding them.
Now that's some terrible grammar. 
https://certbot.eff.org/docs/using.html#re-creating-and-updating-existing-certificates
You can always go to https://crt.sh to view your entire certificate history. You should clear your web browser cache and visit your own domain (or use other certificate viewing tools) to ensure that your new certificate is being served.
2 Likes
OK awesome cheers. How do I know it's updated automatically? When it comes to the renewal for the cert?
1 Like
certbot certificates will always show the cert expiration date.
Checking your site with an external system (like SSL Labs) is other way to confirm that your new cert is actually in use.
And you can see all the certs that have been issued (to date) with https://crt.sh/
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.