bugGNU Octave - Bugs: bug #55402, Certificate for subdomain...

 
 

bug #55402: Certificate for subdomain bugs.octave.org is expired.

Submitter:  None
Submitted:  Sun 06 Jan 2019 02:22:41 PM UTC
   
 
Category:  Octave website Severity:  1 - Wish
Priority:  3 - Low Item Group:  Documentation
Status:  Fixed Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * other
Operating System:  * Any Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 19 Jan 2021 02:33:53 AM UTC, comment #21: 

Thanks for the clarification, Dreamhost manages them automatically.  Octave adopted Let's Encrypt certificates quite "early", maybe some bug with their system has been resolved in the meantime and things work hopefully flawless in the future.  Anyways, thanks for your help with this 🙂

Kai Torben Ohlhus <siko1056>
Group Member
Mon 18 Jan 2021 04:11:24 PM UTC, comment #20: 

After enabling the Let's Encrypt certificates, dreamhost is supposed to update them automatically.  Maybe an update failed?  None of the other domains seemed to have trouble.

John W. Eaton <jwe>
Group administrator
Mon 18 Jan 2021 06:31:43 AM UTC, comment #19: 

Sorry, now it is me who is unresponsive 😇  Two days later and everything is still fine.  Thanks a lot for fixing jwe!

Maybe the combination of both (.htaccess + certificate update) finally worked?!  Webhosting and -design is sometimes magic to me as well.  From the config backup files, I conclude you made a sole change like this


- RewriteRule ^(.*)$ http://savannah.gnu.org/bugs/?group=octave [L,R=301]
+ RewriteRule ^(.*)$ https://savannah.gnu.org/bugs/?group=octave [L,R=301]


As you know, I also have access to the webspace, but only working on the ".htaccess" file was never successful.  Do you manage the Let's Encrypt certificate via the Dreamhost admin portal?  On the webspace I did not find any indication that you update it there.

Kai Torben Ohlhus <siko1056>
Group Member
Sat 16 Jan 2021 04:36:37 PM UTC, comment #18: 

Oh, wait, now they are both working for me.  Argh!  I don't know what I did, other than possibly reinstall the certificate for the domain.  But it is set to auto renew, so I don't know why it would have ever stopped working.

John W. Eaton <jwe>
Group administrator
Sat 16 Jan 2021 04:30:12 PM UTC, comment #17: 

I can change settings if someone knows what to do.

The account is currently set up to

  • use a Let's Encrypt certificate
  • NOT automatically use https
  • have a hosting directory on dreamhost


The hosting directory on dreamhost has a .htaccess file with the lines


RewriteEngine On
RewriteRule ^(.*)$ https://savannah.gnu.org/bugs/?group=octave [L,R=301]


I tried changing to use automatic https and it didn't seem to fix the problem.  Instead, it appeared to make http://bugs.octave.org also fail.

Then I tried disabling hosting and setting up the domain to forward all requests to


https://savannah.gnu.org/bugs/?group=octave


I don't know exactly how that is supposed to work but it still did not seem to redirect properly for both http and https.

I'm out of ideas and with the delays for changing configuration settings (actions from their admin panel typically respond with a message like "your changes will take place in N minutes/hours) it is difficult to know whether subsequent failures are just due to the delay or configuration errors.

After attempting changes and then (I think) putting everything back the way it was originally, it is not working for either http or https currently, at least for me (I did restart my browser; still fails).

John W. Eaton <jwe>
Group administrator
Thu 14 Jan 2021 04:29:49 AM UTC, comment #16: 

Recently, I checked this item again and instead of an error a link to the Dreamhost admin panel is shown

   https://bugs.octave.org/

vs.

   http://bugs.octave.org/ (redirects correctly to https://savannah.gnu.org/bugs/?group=octave)

@jwe: If you don't have time for this, may I take a look at your Dreamhost account (does Dreamhost permit a second admin for the website settings)?

I would love to post the shorter link instead of the verbose one with Savannah, but in times may browsers automatically replace http by https, I seems to "unsafe" to use.

Kai Torben Ohlhus <siko1056>
Group Member
Tue 29 Jan 2019 08:46:21 AM UTC, comment #15: 

As I remember correctly, you don't have root access to the dreamhost server, right?

   https://wiki.octave.org/Project_Infrastructure

So you cannot configure the Apache *.conf file directly?

And by "web panel configuration" you mean this one:

   https://help.dreamhost.com/hc/en-us/articles/215455377-How-do-I-redirect-my-domain-

This somehow looks like it should work afterwards.

Kai Torben Ohlhus <siko1056>
Group Member
Mon 28 Jan 2019 09:11:08 PM UTC, comment #14: 

I don't know how to make this redirect work properly.  Nothing I've tried in the .htaccess file works for me.

The bugs.octave.org domain is a separate DNS record and currently has its own hosting at dreamhost.

I originally tried redirecting through the dreamhost web panel configuration thing but that didn't seem to work for both http and https.  So then I tried switching to a site with actual hosting (instead of redirect only) and using a .htaccess file but that doesn't seem to work either.  I'm out of ideas.

John W. Eaton <jwe>
Group administrator
Sun 27 Jan 2019 11:57:46 AM UTC, comment #13: 

I don't know the reason why, but only


https://bugs.octave.org/


does not redirect, while its http pendant works as expected. I don't know which directory of the webserver is displayed.

Jwe, Maybe you can set in the hosting interface to handle bug.octave.org by the default directory "octave.org", there has already been a redirect rule for the subdomain "bug.*" maybe this works better for both http and https...  But it is just bling guessing.  Is there any documentation about the sever setup?  It looks rather strange to me to not get this simple task done easily :-/

Kai Torben Ohlhus <siko1056>
Group Member
Thu 24 Jan 2019 02:00:51 PM UTC, comment #12: 

OK, since my change in the hosting service redirect settings didn't seem to work with https, I changed it so that we are now hosting bugs.octave.org and I created a .htaccess file there with the line


Redirect 301 / https://savannah.gnu.org/bugs/?group=octave


This appears to work for me now when using a browser but if I use wget there is no indication of a redirect and I just get a nearly empty index.html file.  Is there a better way?

John W. Eaton <jwe>
Group administrator
Mon 21 Jan 2019 10:36:29 AM UTC, comment #11: 

One week is gone and the redirect still goes to  http://savannah.gnu.org.

Jwe, in comment #8 you mentioned that you can manage these settings with the hosting service.  Is there anything you can do about it?  Otherwise just close this report, as we cannot improve anything here ;-)

Kai Torben Ohlhus <siko1056>
Group Member
Mon 14 Jan 2019 05:59:33 PM UTC, comment #10: 

@jwe: Thanks again.  I didn't find those entries in any .htaccess files as well...

At the moment I see the same as Dmitri in comment #8, but lets wait for a day or two and check again. I am afraid there may be caching involved :(


curl https://bugs.octave.org
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://savannah.gnu.org/bugs/?group=octave">here</a>.</p>
</body></html>


Kai Torben Ohlhus <siko1056>
Group Member
Mon 14 Jan 2019 05:20:13 PM UTC, comment #9: 

That is what I see:



wget https://bugs.octave.org
--2019-01-14 11:18:51--  https://bugs.octave.org/
Resolving bugs.octave.org (bugs.octave.org)... 173.236.224.198
Connecting to bugs.octave.org (bugs.octave.org)|173.236.224.198|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://savannah.gnu.org/bugs/?group=octave [following]
--2019-01-14 11:18:51--  http://savannah.gnu.org/bugs/?group=octave
Resolving savannah.gnu.org (savannah.gnu.org)... 209.51.188.79
Connecting to savannah.gnu.org (savannah.gnu.org)|209.51.188.79|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

index.html              [ <=>                ]  38.99K  --.-KB/s    in 0.03s

2019-01-14 11:18:51 (1.21 MB/s) - ‘index.html’ saved [39930]


Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Mon 14 Jan 2019 04:58:24 PM UTC, comment #8: 

Kai, I think it is fixed now.

Where did you see that the redirect went to http://savannah.gnu.org?  It seems that is also redirected (on savannah) to https so how did you notice it?

Anyway, I updated the redirect with the hosting service (this on was not managed with an htaccess file).

John W. Eaton <jwe>
Group administrator
Mon 14 Jan 2019 10:33:47 AM UTC, comment #7: 

@jwe: Thanks for taking care. Now it works for me without certificate errors.

Can you modify the redirect to https as well?  So we have


https://bugs.octave.org --> https://savannah.gnu.org/bugs/?group=octave


Then this item is done for me =)

Kai Torben Ohlhus <siko1056>
Group Member
Mon 14 Jan 2019 02:32:34 AM UTC, comment #6: 

For some reason(?) that I don't remember now, the bugs.octave.org domain had an imported certificate (now expired) instead of using a Let's Encrypt certificate.  Imported certificates are not managed automatically by the hosting service, but the Let's Encrypt certificates are.  I just switched to use a Let's Encrypt certificate and that seems to fix the problem for me.  It should be updated automatically in the future.

John W. Eaton <jwe>
Group administrator
Sun 06 Jan 2019 10:33:08 PM UTC, comment #5: 

@jwe: Do you know how to refresh the https-certificates?  Maybe this can done automatically (Personally, I have a cron job running with certbot for this).

Kai Torben Ohlhus <siko1056>
Group Member
Sun 06 Jan 2019 10:29:41 PM UTC, comment #4: 

I think it may be done in the hosting control panel, jwe may have to take care of this, and see if it can be renewed automatically on a schedule.

Mike Miller <mtmiller>
Group Member
Sun 06 Jan 2019 09:53:48 PM UTC, comment #3: 

You are right Mike.  Where do we refresh those certficates?  I did not find any trace of certbot on "octave.org".

Kai Torben Ohlhus <siko1056>
Group Member
Sun 06 Jan 2019 06:16:50 PM UTC, comment #2: 

The certificate is there, it has simply expired, needs to be renewed.

Mike Miller <mtmiller>
Group Member
Sun 06 Jan 2019 03:10:32 PM UTC, comment #1: 

Confirmed, but I think the solution is to update the Let's Encrypt certificate for this subdomain.

Kai Torben Ohlhus <siko1056>
Group Member
Sun 06 Jan 2019 02:22:41 PM UTC, original submission:  

In etc/icons/org.octave.Octave.appdata.xml, https://bugs.octave.org/ should be changed to http://bugs.octave.org/

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Digest:
   bug dependencies.

 

Carbon-Copy List
  • -email is unavailable- added by apjanke
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by siko1056 (Has the power ;-))
  • -email is unavailable- added by siko1056 (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 16 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-01-18 siko1056 StatusNeed Info Fixed
        Open/ClosedOpen Closed
    2019-04-08 mtmiller Dependencies- bugs #56100 is dependent
    2019-01-26 apjanke Carbon-Copy- Added -email is unavailable-
    2019-01-21 siko1056 Severity2 - Minor 1 - Wish
        StatusConfirmed Need Info
    2019-01-06 siko1056 Carbon-Copy- Added jwe
    2019-01-06 siko1056 SummarySubdomain bugs.octave.org is not covered by https certificate. Certificate for subdomain bugs.octave.org is expired.
    2019-01-06 siko1056 CategoryNone Octave website
        Severity3 - Normal 2 - Minor
        Priority5 - Normal 3 - Low
        Item GroupOther Documentation
        StatusNone Confirmed
        Releasedev other
        Operating SystemGNU/Linux Any
        SummaryAppdata: Link to bug tracker should use http, not https Subdomain bugs.octave.org is not covered by https certificate.

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code