can't access misp url
Closed this issue · 4 comments
heng-zhang-20 commented
conditions
Latest version docker-compose file https://github.com/NUKIB/misp/blob/3ca6a4d8da272cd69dc7377725703e3c04d40872/docker-compose.yml
misp container's logs
[root@ip-xxx misp]# docker-compose up
misp-modules is up-to-date
misp-mysql is up-to-date
misp-redis is up-to-date
Recreating misp ... done
Attaching to misp-modules, misp-mysql, misp-redis, misp
misp | ======================================
misp | MISP develop container image provided by National Cyber and Information Security Agency of the Czech Republic
misp | In case of any problem with this image, please fill issue at https://github.com/NUKIB/misp/issues
misp | ======================================
misp | Warning: 'SECURITY_SALT' environment variable should be at least 32 chars long
misp | Setting system policy to DEFAULT:NO-SHA1
misp | Note: System-wide crypto policies are applied on application start-up.
misp | It is recommended to restart the system for the change of policies
misp | to fully take place.
misp | No syntax errors detected in /var/www/MISP/app/Config/config.php
misp | No syntax errors detected in /var/www/MISP/app/Config/database.php
misp | No syntax errors detected in /var/www/MISP/app/Config/email.php
misp | Syntax OK
misp | [19-Jul-2023 10:24:41] NOTICE: configuration file /etc/php-fpm.conf test is successful
misp |
misp | 2023-07-19 10:24:41,259 - INFO: Connecting to MySQL server mysql:3306
misp | 2023-07-19 10:24:41,263 - INFO: Database schema is already created.
misp | Executing all updates to bring the database up to date with the current version.
misp | All updates completed.
misp | Updating all JSON structures.
misp | Successfully connected to Redis.
misp | gpg: keybox '/var/www/MISP/.gnupg/pubring.kbx' created
misp | gpg: /var/www/MISP/.gnupg/trustdb.gpg: trustdb created
misp | 2023-07-19 10:24:41,787 INFO Included extra file "/etc/supervisord.d/misp.ini" during parsing
misp | 2023-07-19 10:24:41,787 INFO Set uid to user 0 succeeded
misp | 2023-07-19 10:24:41,792 INFO RPC interface 'supervisor' initialized
misp | 2023-07-19 10:24:41,792 CRIT Server 'unix_http_server' running without any HTTP authentication checking
misp | 2023-07-19 10:24:41,793 INFO supervisord started with pid 1
misp | Galaxies updated.
misp | Noticelists updated.
misp | Warninglists updated.
misp | Taxonomies updated.
misp | ObjectTemplates updated.
misp | ObjectRelationships updated.
misp | All JSON structures updated. Thank you and have a very safe and productive day.
misp | 2023-07-19 10:24:42,795 INFO spawned: 'rsyslog' with pid 62
misp | 2023-07-19 10:24:42,798 INFO spawned: 'httpd' with pid 63
misp | 2023-07-19 10:24:42,800 INFO spawned: 'jobber' with pid 64
misp | 2023-07-19 10:24:42,803 INFO spawned: 'default' with pid 65
misp | 2023-07-19 10:24:42,806 INFO spawned: 'email_00' with pid 68
misp | 2023-07-19 10:24:42,810 INFO spawned: 'email_01' with pid 74
misp | 2023-07-19 10:24:42,817 INFO spawned: 'email_02' with pid 77
misp | 2023-07-19 10:24:42,820 INFO spawned: 'cache' with pid 78
misp | 2023-07-19 10:24:42,824 INFO spawned: 'prio_00' with pid 81
misp | 2023-07-19 10:24:42,827 INFO spawned: 'prio_01' with pid 82
misp | 2023-07-19 10:24:42,830 INFO spawned: 'prio_02' with pid 83
misp | 2023-07-19 10:24:42,833 INFO spawned: 'update' with pid 85
misp | 2023-07-19 10:24:42,836 INFO spawned: 'php-fpm' with pid 86
misp | 2023-07-19 10:24:42,837 INFO reaped unknown pid 32 (exit status 0)
misp | 2023-07-19 10:24:44,232 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: jobber entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: default entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: email_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: email_01 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: email_02 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: cache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: prio_00 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: prio_01 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: prio_02 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: update entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
misp | 2023-07-19 10:24:44,232 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
response nothing
[root@ip-xxx misp]# docker-compose ps
Name Command State Ports
-----------------------------------------------------------------------------------------------------------------
misp /usr/local/bin/docker-entr ... Up (healthy) 127.0.0.1:50000->50000/tcp, 127.0.0.1:8080->80/tcp
misp-modules /home/misp-modules/.local/ ... Up (healthy) 6666/tcp
misp-mysql docker-entrypoint.sh mariadbd Up 3306/tcp
misp-redis docker-entrypoint.sh redis ... Up 6379/tcp
[root@ip-xxx misp]# curl http://127.0.0.1:8080
[root@ip-xxx misp]#
kanekennedy commented
I have the same issue, something has been broken with the update 5 days ago.
I have tried with the testing instruction and using external DB to no difference, logs never go past php-fpm line.
Benni0 commented
Hi,
I've tried both - the default image from git and an image built by myself and used the preconfigured docker compose file without any changes.
Both images have worked without any issues.
@heng-zhang-20
From my point of view your output looks good.
The empty output from curl is ok, because MISP responds with a redirect (HTTP 302) and curl doesn't follow redirects by default.
Please use curl http://localhost:8080 -L to check the response.
You can also use the verbose mode curl http://localhost:8080 -v to see the redirect.
heng-zhang-20 commented
@Benni0 You are right.
heng-zhang-20 commented
@kanekennedy Try access http://your-ip:8080 through your browser.