-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not login to caldera 5.0 #2984
Comments
OS version where is docker installed.
|
And what shoul it be correct IP for the |
I'm also facing the same issue I put in the login credentials and nothing happens but I'm not on the docker build just on ubuntu build logs:
|
@sidomir7 type http://0.0.0.0:8888 in browser, instead of http://localhost:8888 |
works, thanks @abhra101 |
@Abdelrahman671 |
The solution of typing 0.0.0.0 instead of localhost works if you want to access in the same machine you have deployed Caldera. In case you want to access from other PC, you have to change in the file "conf/default.yml" the line Hope this works. |
Solution for me was add IP and port for server to |
The problem started from the commit 1302d33. Until that commit, the Starting from that commit, the Vue.js Of course, putting a single fixed IP address in the My suggestion is the following:
def configure_magma_env_file():
logging.info("Setting VueJS environment file.")
url = BaseWorld.get_config("app.frontend.api_base_url")
with open(f"{MAGMA_PATH}/.env", "w") as fp:
fp.write(f"VITE_CALDERA_URL={url}") I made a PR here related to this issue. |
Hopefully closed by #2994. Reopen if still an issue. Apologies for delay. |
use this step and I can login caldera
ex: ability_refresh: 60
api_key_blue: BLUEADMIN123
api_key_red: ADMIN123
app.contact.dns.domain: mycaldera.caldera
app.contact.dns.socket: 0.0.0.0:8853 <--- hostip
app.contact.gist: API_KEY
app.contact.html: /weather
app.contact.http: http://0.0.0.0:8888 <--- hostip
app.contact.slack.api_key: SLACK_TOKEN
app.contact.slack.bot_id: SLACK_BOT_ID
app.contact.slack.channel_id: SLACK_CHANNEL_ID
app.contact.tunnel.ssh.host_key_file: REPLACE_WITH_KEY_FILE_PATH
app.contact.tunnel.ssh.host_key_passphrase: REPLACE_WITH_KEY_FILE_PASSPHRASE
app.contact.tunnel.ssh.socket: 0.0.0.0:8022 <--- hostip
app.contact.tunnel.ssh.user_name: sandcat
app.contact.tunnel.ssh.user_password: s4ndc4t!
app.contact.ftp.host: 0.0.0.0 <--- hostip
app.contact.ftp.port: 2222
app.contact.ftp.pword: caldera
app.contact.ftp.server.dir: ftp_dir
app.contact.ftp.user: caldera_user
app.contact.tcp: 0.0.0.0:7010 <--- hostip
app.contact.udp: 0.0.0.0:7011 <--- hostip
app.contact.websocket: 0.0.0.0:7012 <--- hostip
app.frontend.api_base_url: http://localhost:8888 <--- hostip |
Solution Using Python Method:I ran into a similar issue and decided to provide some more detail on how to solve the problem.
|
run this in your caldera folder find . -type f -exec grep -l "http://localhost:8888/" {} ; | xargs -I {} sed -i "s/http://localhost:8888/http://FILLYOURIPADDRESS:8888/g" {} |
I've also tried this solution, but it didn't work. I've followed all the other instructions as well, but I'm still back at square one. Has anyone managed to solve this issue? Is there a working workaround? |
sudo python3 server.py 2025-01-07 17:39:31 - WARNING (warnings.py:109 _showwarnmsg) /usr/local/lib/python3.10/dist-packages/asyncssh/crypto/cipher.py:30: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from cryptography.hazmat.primitives.ciphers.algorithms in 48.0.0. 2025-01-07 17:39:32 - INFO (contact_gist.py:70 start) Invalid Github Gist personal API token provided. Gist C2 contact will not be started. 2025-01-07 17:41:48 - INFO (logging.py:92 log) [conn=0] Accepted SSH client connection Anyone help me out what happening is here? I tried everything I update the SSH file. Remove the caldera and again reinstall the caldera 2-3 time, but "SSH connection error" still there. I don't know what to do now. Please help! |
Hi, I can not login to the caldera web app wit red or blue account.
I followed Docker Deployment from README.
This are logs from docker build.
The text was updated successfully, but these errors were encountered: