Upon logging into a ghost installation on a raspberry pi at .diode.link, or at . (per https://support.diode.io/article/6pctb40wj8), the following error is displayed upon successful login:
If I navigate away from /ghost/#/signin to just /ghost, the system allows me into the admin area, so I know the login was successful, just the browser got an error making it look like it failed.
These errors do not exist when using http://localhost to login. These errors exist on all three different ghost versions I tested when published via Diode. There are additional browser errors, perhaps from the same root cause, that are raised if I try to add a featured image to a post. If I retry enough times, it works.
The root cause may be ghost trying to re-use cached connections that the Diode web2:web3 gateway proxy has closed.
Upon logging into a ghost installation on a raspberry pi at.diode.link, or at . (per https://support.diode.io/article/6pctb40wj8), the following error is displayed upon successful login:
If I navigate away from /ghost/#/signin to just /ghost, the system allows me into the admin area, so I know the login was successful, just the browser got an error making it look like it failed.
These errors do not exist when using http://localhost to login. These errors exist on all three different ghost versions I tested when published via Diode. There are additional browser errors, perhaps from the same root cause, that are raised if I try to add a featured image to a post. If I retry enough times, it works.
The root cause may be ghost trying to re-use cached connections that the Diode web2:web3 gateway proxy has closed.