Https Protocol Request

[Flick]

I tried that and it didn't work. The embed codes need to have the nabble code in them, then nabble should redirect to the designated board.

[Harvey]

Raven<Nabble> wrote

I'll ask someone else and see if there's a fix.

Thank you for being persistent. This is really crucial.

[Raven<Nabble>]

Flick wrote

I tried that and it didn't work. The embed codes need to have the nabble code in them, then nabble should redirect to the designated board.

Can you please change it so that I can take a look?
If it's correct, you should get a 404 error which was what Harvey and Gary were getting (some link inside the iframe is broken). Then I'll see if I can find a solution for that.

[Flick]

It works.  My forum finally loaded with the last fix provided by Raven. My site and the forum are now both using https and fully functioning. Thanks to Raven and GregChapman and others who persisted in keeping this problem out there until it was resolved. Here's what my new embed code now looks like:

<a id="nabblelink" href="https://forums.example.com/">My Forum Title</a>

<script src="https://forums.example.com/embed/f1"></script>

[Gary Lewis]

Yippee!!  That has to be a good feeling.  I know how concerned I was when my forum was sorta down for 12 hours, so I can't imagine how bad it was for you.  

[Harvey]

What is the next step?

If you do mine now it should be ok until my developer can flip the outer page to https right?  He can do it Monday am.

[Gary Lewis]

I'm not in a hurry, so I'm happy to wait until Harvey's is done - or even another if that is needed.  I think I'm last on the list.

[Flick]

While waiting for your developer, you can take care of the C-name issues in the interim. That won't affect your current operation while at the same time eliminate one step you will have to do later.

 

Reven wrote

You need to go to your dns records and set a cname record pointing a subdomain to (in your case) n7.nabble.com. The domain should redirect to the Nabble homepage if configured correctly.

[Harvey]

Not sure what you mean. I think my URL already has a C name?

http://forum.nyskiblog.com

one thing I do see is that I have this in my code and you don't:

type="text/javascript"

so currently my code looks like this:

<a id="nabblelink" href="http://forum.nyskiblog.com/">NYSkiForums</a>
<script src="http://forum.nyskiblog.com/embed/f123456" type="text/javascript"></script>

Can't I just change it to https?

[Flick]

Your embed code should look exactly like mine except for replacing example.com with your domain name. Notice how my URL has https in it whereas your does not. That's a change you'll make once you are running on https. You can contact your host and ask them to make a C-name entry for your new SSL address which will include https in the URL and point to n7.nabble.com

[Flick]

The only bug I see with the new https is small. When you visit a thread at the bottom of the last message a "Return to the Forum" button appears which takes you back from whence you came. It doesn't work. Nothing happens when you click on it. A quick fix on that would be nice. Thanks Raven.

[Raven<Nabble>]

SIgnup activation links are still broken because they point to the subdomain which has broken links, broken redirect. This is some sort of bug. I'll have to look into this.

[Raven<Nabble>]

Flick it has been fixed, things appear to be all working now.

[Harvey]

Raven what does this mean for the rest of us? Please let me know the timing before you move.

[Raven<Nabble>]

Assuming nothing else is broken, I should be able to do everyone else's sites. Your site, Gary's site etc.
Let me know when you're ready, I can do it tomorrow or whenever you're ready.

[Gary Lewis]

If there is nothing else to do, then I'm ready.  But I'm in no hurry so put Harvey first if he's ready.

However, the "outage" last Wednesday night was painful, so if there's a potential for a problem then I'm a bit cautious.

[Harvey]

I guess if you think you are ready do mine too.

[Flick]

Thank you for all your hard work. I'm testing the message board out and everything seems to be working even better than it did before. I just came across one you missed however:  the cancel button doesn't work. I just tested the reply button and decided not to leave a message so I hit the cancel button and nothing happen. The cancel button doesn't work anywhere. Sorry for creating so much work for you but you did ask.

[goldenring20000]

Is there a way to solve the problem on blogger blog?
Just changing to HTTPS doesn't help
Any hope for us?

[Raven<Nabble>]

Flick wrote

 The cancel button doesn't work anywhere.

Fixed

goldenring20000 wrote

Is there a way to solve the problem on blogger blog?

No, I don't believe there is anything we can do for Blogger.