When I open a ticket on stg.pagure.io, e.g. https://stg.pagure.io/pagure/issue/12 , I see these errors in my Firefox console:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://stg.pagure.io:8088/pagure/issue/12. (Reason: CORS request did not succeed). Firefox can’t establish a connection to the server at https://stg.pagure.io:8088/pagure/issue/12.
When I try to open https://stg.pagure.io:8088/pagure/issue/12 it says:
Did Not Connect: Potential Security Issue Websites prove their identity via certificates, which are valid for a set time period. The certificate for stg.pagure.io:8088 expired on 8/7/2021. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Looks like the certificate needs refreshing.
¯\_(ツ)_/¯ It doesn't block me, I just noticed it.
¯\_(ツ)_/¯
Actually, a similar problem seems to be on production Pagure as well. For example: https://pagure.io/pagure/issue/5212
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://pagure.io:8088/pagure/issue/5212. (Reason: CORS request did not succeed).
But connection to https://pagure.io:8088/pagure/issue/5212 simply times out, instead of giving a certificate error.
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
The expired cert might be easy to fix, but no idea on the CORS header... CC @pingou ?
I fixed the expired cert and the stuck pagure_ev services.
The only thing left here is the CORS error. I've filed https://pagure.io/pagure/issue/5214 on that. Please do follow along on that...
Thanks for the report.
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.