Closed Bug 1489400 Opened 7 years ago Closed 7 years ago

Change dns information for www.seamonkey-project.org

Categories

(Infrastructure & Operations :: Runtime, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: rtucker)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/19/6999])

www.seamonkey-project.org needs to migrate off the current server (genericadm?) I have a system currently being set up with an ip. what needs to be done here: 1) change the IP of the www.seamonkey-project.org dns entry to 52.179.195.254 2) obtain a copy of the certificates (crt and key) for www.seamonkey-project.org
Blocks: 1489399
Component: Web Site → Runtime
Product: Cloud Services → Infrastructure & Operations
QA Contact: smani
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/19/6999]
(In reply to Edmund Wong (:ewong) from comment #0) > www.seamonkey-project.org needs to migrate off the current server > (genericadm?) > > I have a system currently being set up with an ip. > > what needs to be done here: > > 1) change the IP of the www.seamonkey-project.org dns entry to > 52.179.195.254 > > 2) obtain a copy of the certificates (crt and key) for > www.seamonkey-project.org I'm guessing you need the crt and key 1st so that you can configure the new webserver. This site is using the generic SAN cert and will need a new one issued. Once those have been done, the DNS change is trivial openssl s_client -connect seamonkey-project.org:443 CONNECTED(00000005) depth=1 C = US, O = DigiCert Inc, CN = DigiCert SHA2 Secure Server CA verify error:num=20:unable to get local issuer certificate verify return:0 --- Certificate chain 0 s:/C=US/ST=California/L=Mountain View/O=Mozilla Foundation/OU=WebOps/CN=generic-san.mozilla.org i:/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA 1 s:/C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA
Assignee: nobody → rtucker
><(((º> bin/autocert create -o f -b 1489400 seamonkey-project.org -v2 certs: - seamonkey-project.org@7e46413b: authority: digicert: order_id: 3420580 bug: '1489400' common_name: seamonkey-project.org destinations: {} expiry: Thu, 12 Sep 2019 00:00:00 GMT modhash: 7e46413bbdfe82a2131b9a1f5f6fe20a tardata: seamonkey-project.org@7e46413b.tar.gz: seamonkey-project.org@7e46413b.crt: CRT seamonkey-project.org@7e46413b.csr: CSR seamonkey-project.org@7e46413b.key: KEY timestamp: Fri, 07 Sep 2018 23:33:23 GMT
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
(In reply to Scott Idler [:sidler] [:escote] from comment #2) > ><(((º> bin/autocert create -o f -b 1489400 seamonkey-project.org -v2 > certs: > - seamonkey-project.org@7e46413b: > authority: > digicert: > order_id: 3420580 > bug: '1489400' > common_name: seamonkey-project.org > destinations: {} > expiry: Thu, 12 Sep 2019 00:00:00 GMT > modhash: 7e46413bbdfe82a2131b9a1f5f6fe20a > tardata: > seamonkey-project.org@7e46413b.tar.gz: > seamonkey-project.org@7e46413b.crt: CRT > seamonkey-project.org@7e46413b.csr: CSR > seamonkey-project.org@7e46413b.key: KEY > timestamp: Fri, 07 Sep 2018 23:33:23 GMT Hi :sidler, where can I get this cert?
Re-opening to ensure Edmund gets the cert.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Shyam Mani [:fox2mike] from comment #4) > Re-opening to ensure Edmund gets the cert. Just got the cert from :sidler. Thanks everyone! It's now installed; but need to wait until the dns expires on the old ip.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Forgot to ask.. Was the dns change done?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Edmund Wong (:ewong) from comment #6) > Forgot to ask.. Was the dns change done? I updated the IP for the A record www.seamonkey-project.org I think you should be good to go here.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
The site is responding with 403s now, looks like the webserver configuration is not right. :ewong could you have a look?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Flags: needinfo?(ewong)
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Alberto del Barrio from comment #8) > The site is responding with 403s now, looks like the webserver configuration > is not right. > :ewong could you have a look? Yes, it's my bad. Part webserver, part cronjob misfire. It's now fixed. Thanks :rtucker, :escote! Appreciate the help with this.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Flags: needinfo?(ewong)
Resolution: --- → FIXED
Blocks: 1490540
You need to log in before you can comment on or make changes to this bug.