Remote connection to the caldera server http://ipcaldera:8888 does not log in

[cris1198]

I set up the boiler server on a Debian machine, I want to connect to the server from another PC but when I access http://ipremotecaldera:8888 through the web it cannot log in, it stays there hanging, how can I solve it?

[github-actions]

Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/

[elegantmoose]

See if the docs on server config help: https://caldera.readthedocs.io/en/latest/Server-Configuration.html#configuration-file

[elegantmoose]

@cris1198 did you pull 5.0 or master?

*Try pulling down master and see these notes: https://caldera.readthedocs.io/en/latest/Server-Configuration.html#configuration-file

[elegantmoose]

Apologies for late reply.

[Ch1l3n0]

I ran into a section in the Caldera documents that describes this type of behavior when the app.frontend.api_base_url is left at its default setting. If you look at the developer tools, network tools, there's a failed 302 redirect as your browser tries to access the default http://localhost:8888. The docs say:
The value set for app.frontend.api_base_url is used to configure the Caldera v5 Vue UI when the Caldera server is started with the --build flag. It has been observed that in some situations the default configuration values can cause the UI to appear unresponsive due to misrouted requests. This mainly occurs when the server is running on a host different than the UI is being accessed from. In these cases, the value should be changed to the appropriate URL for the UI to route requests to.

[uruwhy]

@cris1198 Can you confirm whether or not updating app.frontend.api_base_url fixed your issue?

[ns0r]

I too have this problem, and modifing the app.frontend.api_base_url config parameter made no difference.

[uruwhy]

I too have this problem, and modifing the app.frontend.api_base_url config parameter made no difference.

@ns0r If you open up the developer console on your CALDERA login page and attempt to log in, what console error(s) are you seeing?

[uruwhy]

I too have this problem, and modifing the app.frontend.api_base_url config parameter made no difference.

@ns0r Did you modify the configuration file while CALDERA was still running? If so, any manual changes in the yaml file will be overwritten when the server stops. You can confirm this by double-checking the contents of the config file when the server isn't running.

[ns0r]

I was able to fix my problem by changing the VITE_CALDERA_URL from http://0.0.0.0:8888 to http://myipaddress:8888 in the /plugins/magma/.env file, and doing a --fresh --build. This fixed the login problem. However the app still isn't looking right. It can't see any agents, etc.

[uruwhy]

I was able to fix my problem by changing the VITE_CALDERA_URL from http://0.0.0.0:8888 to http://myipaddress:8888 in the /plugins/magma/.env file, and doing a --fresh --build. This fixed the login problem. However the app still isn't looking right. It can't see any agents, etc.

@ns0r
Can you send a screenshot of what your login page looks like?
My fresh install looks something like this (no agents currently beaconing in, no previous operations):

[elegantmoose]

reopen if issue still persists.