Closed Bug 1178498 Opened 9 years ago Closed 9 years ago

webfwd.org's certificate expired

Categories

(Infrastructure & Operations :: SSL Certificates, task)

Product:
Infrastructure & Operations
Component:
SSL Certificates
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: aryx, Assigned: rwatson)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1370] ) 

Open https://webfwd.org/

webfwd.org uses an invalid security certificate.
The certificate expired on 29.06.2015 07:03. The current time is 29.06.2015 23:42.
(Error code: sec_error_expired_certificate)
Component: Other → WebOps: SSL and Domain Names
Product: Websites → Infrastructure & Operations
Version: unspecified → other
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1370]
Didem: Do we still need to maintain HTTPS access for webfwd.org?  If so, I'll need to renew the certificate and associate it with a cost center.
Flags: needinfo?(dersoz)
QA Contact: smani
Assignee: nobody → rwatson
Tempted to WONTFIX. Have contacted Didem via email and IRC with no response. This has been out of SSL for over 3 weeks now.
Time out. Reopen with info if this is still needed.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
--On September 11, 2015 at 9:24:37 AM -0700 Didem Ersoz <dersoz@mozilla.com> wrote:

> I totally and completely agree with Diane that we have very valuable
> resources on that site and it is important to keep them available,
> preferably on the same domain.
Status: RESOLVED → REOPENED
Flags: needinfo?(dersoz)
Resolution: INCOMPLETE → ---
Apologies for the delay in getting back on this topic, but yes, we have valuable resources that are still available to entrepreneurs on the webfwd.org site. So, we should keep it available. 

I see that you also asked for a cost center. What was the cost center used before? webfwd.org was part of the Mozilla Labs, but it doesn't exist anymore. What is the cost associated to renew the certificates, and keep the website available?

Thanks,
Didem
Hello! 

Due to the nature of the domain, I will add this to the IT cost centre. 
I have a question before I renew this. The old cert was a SAN cert which also included the domains:
webfwd.net, www.webfwd.net, beta.webfwd.org, beta.webfwd.net

Do you still still need these on the cert or do you just need webfwd.org?

I'll get this done this week for you.
Flags: needinfo?(dersoz)
Flags: needinfo?(dtate)
I think webfwd.org is sufficient. What do you think Diane?
Flags: needinfo?(dersoz)
Hi Ryan,

I'd like to edit my response. We should keep: 

webfwd.org
beta.webfwd.org 

beta domain is where we see the changes when we make updates to the website before pushing them to the production site.

thanks,
didem
agree with didem - we also need to keep blog.webfwd.org, so in summary, keep:

webfwd.org
beta.webfwd.org
blog.webfwd.org

thanks so much all!
Flags: needinfo?(dtate)
I've applied for the certs. Just waiting for digicert to verify the domain.
thanks so much all
Well. 

I've re-added the cert and currently: 
https://webfwd.org is working again...

One thing I did notice is, that we are actually unable to do "blog.webfwd.org" as Mozilla does not host it (it's currently pointing to a tumblr):

host -i blog.webfwd.org
blog.webfwd.org is an alias for domains.tumblr.com.

So other than that, I think we are all set.
excellent - and the blog is working fine (thanks tumblr ;) - yay!
yay
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.