API endpoint not available

[Mike-Zimmermann-mg]

Hi,
first I would like to thank you for your work.
I am not completely sure if the actual problem is on your site, but at the moment the API endpoint is not available.
BR, Mike

[derhuerst]

Thanks for reporting this.

I'm aware of this downtime and arguing with my hosting providers & my bank to get this running again. I thought about spinning up a replacement instance because it may take another day.

[derhuerst]

I'm about to set up fallback.transport.rest running with a different hoster. There may be additional difficulties as VBB just changed all their station IDs to a new format, which their API doesn't use.

[derhuerst]

It's up, but i'll have to restart it once more in the next 10 min.

Sorry for the inconvenience. I know it's hard to trust some service's reliability if it gets down for 1,5 days. This was an exceptional outage because my bank switched SEPA & credit card numbers and messed a few things up.

[Mike-Zimmermann-mg]

No need to excuse. These kind of things could happen.
Running the curl command to fetch stationIDs gives me back this message:
curl: (51) SSL: no alternative certificate subject name matches target host name 'transport.rest'

Don't get me wrong I don't want to put any pressure on this.
This is just, what I found.

I think the certificat still leads to fallback.transport.rest

[derhuerst]

Ah, I CNAMEd transport.rest to fallback.transport.rest. That's why it doesn't work. Please use fallback.transport.rest.

[derhuerst]

I can access my original instances again. Will get them running again as quickly as possible.

[derhuerst]

transport.rest works again. Will shut fallback.transport.rest down in 1 or 2 days.

As i said earlier, there's some weird things still happening because of the new VBB IDs. Working on it.

[derhuerst]

Please note that I will migrate to vbb.transport.rest soon. The responses will have a new format I will push docs about today.