-
Notifications
You must be signed in to change notification settings - Fork 171
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
my_ip:7474 >> This site can’t be reached #447
Comments
Any news on this? |
Go same my docker-compose.yml: services: replica: networks: My neo4j.conf Setting that specifies how much memory Neo4j is allowed to use for the page cache.dbms.memory.pagecache.size=100M Setting that specifies the initial JVM heap size.dbms.memory.heap.initial_size=100M Strategy that the instance will use to determine the addresses of other members.causal_clustering.discovery_type=DNS The network addresses of an initial set of Core cluster members that are available to bootstrap this Core or Read Replica instance.If the DNS strategy is used, the addresses are fetch using the DNS A records.causal_clustering.initial_discovery_members=tasks.lan:5000 Address (the public hostname/IP address of the machine)and port setting that specifies where this instance advertises for discovery protocol messages from other members of the cluster.causal_clustering.discovery_advertised_address=$(hostname -i) Address (the public hostname/IP address of the machine)and port setting that specifies where this instance advertises for Raft messages within the Core cluster.causal_clustering.raft_advertised_address=$(hostname) Address (the public hostname/IP address of the machine)and port setting that specifies where this instance advertises for requests for transactions in the transaction-shipping catchup protocol.causal_clustering.transaction_advertised_address=$(hostname) Enable server side routingdbms.routing.enabled=true Use server side routing for neo4j:// protocol connections.dbms.routing.default_router=SERVER The advertised address for the intra-cluster routing connector.dbms.routing.advertised_address=$(hostname) Have tried several stuff but web interface is only available from inside the container. |
installed it on docker
backend | yarn run v1.22.19
backend | $ node build/
maintenance | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
maintenance | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
maintenance | /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
maintenance | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
maintenance | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
maintenance | /docker-entrypoint.sh: Configuration complete; ready for start up
maintenance | 2023/06/22 16:11:14 [notice] 1#1: using the "epoll" event method
maintenance | 2023/06/22 16:11:14 [notice] 1#1: nginx/1.25.1
maintenance | 2023/06/22 16:11:14 [notice] 1#1: built by gcc 12.2.1 20220924 (Alpine 12.2.1_git20220924-r4)
maintenance | 2023/06/22 16:11:14 [notice] 1#1: OS: Linux 5.4.0-150-generic
maintenance | 2023/06/22 16:11:14 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker processes
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 20
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 21
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 22
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 23
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 24
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 25
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 26
maintenance | 2023/06/22 16:11:14 [notice] 1#1: start worker process 27
webapp | yarn run v1.22.19
webapp | $ cross-env NODE_OPTIONS=--openssl-legacy-provider nuxt start
webapp |
webapp | WARN No .env file found in /app.
webapp |
backend | Warning: Middlewares will not try to send mails.
backend | Warning: Sentry middleware inactive.
webapp | ? Errors will not be logged because no DSN has been provided
webapp | ? Started logging errors to Sentry
webapp | ? Listening on: http://192.168.0.4:3000/
backend | ? Server ready at http://localhost:4000/
backend | ? Subscriptions ready at ws://localhost:4000/graphql
neo4j | 2023-06-22 16:11:21.452+0000 WARN Unrecognized setting. No declared setting with name: dbms.allow_format_migration
neo4j | 2023-06-22 16:11:21.500+0000 INFO Starting...
neo4j | 2023-06-22 16:11:22.319+0000 INFO This instance is ServerId{2afae5de} (2afae5de-7e24-4a33-b6fd-45c641bacc8e)
neo4j | 2023-06-22 16:11:24.009+0000 INFO ======== Neo4j 4.4.21 ========
neo4j | 2023-06-22 16:11:32.629+0000 INFO Performing postInitialization step for component 'security-users' with version 3 and status CURRENT
neo4j | 2023-06-22 16:11:32.630+0000 INFO Updating the initial password in component 'security-users'
neo4j | 2023-06-22 16:11:34.649+0000 INFO Called db.clearQueryCaches(): Query cache already empty.
neo4j | 2023-06-22 16:11:42.729+0000 INFO Bolt enabled on 0.0.0.0:7687.
neo4j | 2023-06-22 16:11:43.784+0000 INFO Remote interface available at http://localhost:7474/
neo4j | 2023-06-22 16:11:43.790+0000 INFO id: 5E36093F72525C74C3F5AE5195B4F60B2D5C06B53AD9100FA89FFE73A34C0093
neo4j | 2023-06-22 16:11:43.790+0000 INFO name: system
neo4j | 2023-06-22 16:11:43.791+0000 INFO creationDate: 2023-06-22T12:47:19.375Z
neo4j | 2023-06-22 16:11:43.791+0000 INFO Started.
http://localhost:4000/
and http://localhost:7474
not working
The text was updated successfully, but these errors were encountered: