New self-hosted instance tries to connect to api.m...
# supportc
codingtom
10/19/2023, 7:15 PMI'm trying to deploy a new self-hosted instance for our production environment. Everything seems to deploy fine, but it's not clear that variable replacement works for the application's static files. When I open the app URL in the browser, error messages appear in the console that the app is trying to connect to api.medplum.com, which fails the content security policy. Obviously, it should be instead connecting to the hosted API (which is running just fine, and returns an OK).
codingtom
10/19/2023, 7:15 PMA bunch of messages like this - I'm not including the CSP because it correctly references our actual API server
codingtom
10/19/2023, 7:17 PMI'm being forced to use the 2.1.1 CLI, because anything later results in this same error message from a previous open thread: https://discord.com/channels/905144809105260605/1161375729804656640
codingtom
10/19/2023, 7:18 PMPretty strange - basically the
baseUrlcodingtom
10/19/2023, 8:40 PMShoot, our development environment app is now broken with the same error after updating
r
rahul1
10/19/2023, 9:39 PMHi @codingtom - we're very sorry about the error. There was a bug in our deploy process for 2.1.5 that caused the ap to always point to
api.medplum.comc
codingtom
10/19/2023, 9:57 PMAhh gotcha - I see that the cli always grabs and uploads assets from the latest version. I can probably wait for 2.1.6 release, thanks!
codingtom
10/19/2023, 9:59 PMWill make sure I check issues next time 😅 sorry for the noise!
r
rahul1
10/19/2023, 10:10 PMNo need to apologize, this was our fault
rahul1
10/19/2023, 10:10 PMWe should be able to release 2.1.6 by EOD today
rahul1
10/20/2023, 6:51 PM173 Views