#9496 Was translate Staging redirect removed?
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by jibecfed.

Describe what you would like us to do:

When we first installed Weblate for Fedora, we used https://translate.stg.fedoraproject.org/hooks/pagure/

To interact with Pagure, we had to use this URL as a webhook: https://translate.stg.fedoraproject.org/hooks/pagure/

But this staging URL now leads to a 404.

When do you need this to be done by? (YYYY/MM/DD)

Could you eith list all pagure project with staging URL or restore the redirection?

Example issue: https://pagure.io/fedora-l10n/tickets/issue/7

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-trouble, medium-gain, ops

3 years ago

So, since we moved datacenters we completely redeployed out staging env in the new datacenter.

I don't understand how this site is setup. ;(

Ah, it looks like it's not, it's just a dns record for weblate?

% host translate.fedoraproject.org
translate.fedoraproject.org is an alias for fedora.weblate.cloud.
fedora.weblate.cloud has address
fedora.weblate.cloud has IPv6 address 2a01:4f8:c2c:9ea3::1

So should translate.stg.fedoraproject.org point to the same place?

hello, yes, same destination=2E


Metadata Update from @kevin:
- Issue assigned to kevin

3 years ago

ok. I have done this, but... the certificate there seems expired?

I don't think thats on our side... but if it is let us know. :)

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

3 years ago

which certificate? translate=2E fp=2Eo looks good to me

That was letsencrypt, so I guess it will renew itself now the DNS is back.

Login to comment on this ticket.

Boards 1
ops Status: Done