#7744 Could we please point ask.fedoraproject.org to the new Discourse instance.
Closed: Fixed by smooge. Opened by ankursinha.

Hello,

Could we please have ask.fedoraproject.org to point to the new Discourse instance: https://payments.discourse.org/c/8e5be4f6869317ceaa901e18479fc27c/subscription/dns_instructions

Could we also have askbot.fedoraproject.org point to the askbot instance? (I don't know how this is to be done)

CC: @mattdm @bex


We can look at doing so
1. After @mattdm @bex says we are to do so.
2. After freeze for f30 unless it is an emergency and we can do so with a freeze break.

We can look at doing so
1. After @mattdm @bex says we are to do so.

@mattdm is already on board: https://askbeta.fedoraproject.org/t/fedora-30-releases-on-30-april-2019-flip-ask-fedoraproject-org-to-here/241/2?u=franciscod

  1. After freeze for f30 unless it is an emergency and we can do so with a freeze break.

It'll be good to have it done before the release so that users are sent to the new instance after they've installed/upgraded to F30.

Sorry, we thought we had more time and got caught off-guard a bit.

Just had a thought: could we make askbeta.fp.o point to ask.fp.o too so that links on the commblog etc. don't break?

Yeah, for the record, ACK on this request.

It's not an emergency but as @ankursinha notes it'd be nice to have in place so people can bring any questions with the new release there.

For the record, I am also ACK and +1 to FBR

I am working on this today.

Metadata Update from @smooge:
- Issue assigned to smooge

There is no askbot.fedoraproject.org so I am not sure what this was/is.
-- Edited NEVER MIND. I rolled a 1 on my reading skills check and critically fumbled.

Please DO NOTE: the URL will need to be updated on the Discourse instance, and when that happens, the OIDC client needs to be updated with the new URL as well!
EDIT: seems the latter part doesn't have to be done... I already did that when I created the client ID. We do want to make sure the old URL gets removed, but that's not a priority.

OK DNS changes are rolling out. please test.

Changes seem to be deployed and working

Metadata Update from @smooge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

+1 ask.fedoraproject.org

Not been able to get to askbot.fp.o yet, but this really isn't too important at all at the moment.

Thanks very much!

askbot doesn't have a certificate for that url.
That will need to be requested from the askbot people to set up.

Actually you might not be able to talk with askbot for 2 reasons.
1. The certificate (what puiterwijk said above).
2. The virtual host it is trying to answer is ask.fedoraproject.org. Going to askbot would not work as the webserver wouldn't know

Both of those would need to be gotten from the askbot people.

Ah, OK---I don't know who speaks to the askbot people. @mattdm @bex : any ideas?

@ankursinha I'm on it.

Also, btw, logins are currently broken on the new ask. Patrick is working on it as we speak.

@ankursinha @hhlp Can you tell me where we landed on the "require FAS account or not" situation? The current auth problem is related to that. Which way we go to fix it depends on that :)

Ah looks like the answer is: FAS is supposed to be required, and the problem is with accounts like mine that snuck in previously. We'll fix mine, and then admins can fix anyone else with the same problem case-by-case.

Metadata