cant connect to rpc containers as well as unable to open doc defined in readme

[Arhamtahir]

https://docs.polygon.technology/cdk/get-started/quickstart-validium/pos

also i got rpc url error VM62:1 MetaMask - RPC Error: Expected an array with at least one valid string HTTPS url 'rpcUrls', Received:
http://localhost:8123 when try to connect metamask through http://localhost:8088 bridge

previously it was connected to http url but now it says https error

[Arhamtahir]

                              zkevm-data-node-db

1de34f52f643 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-json-rpc
a7c1244e7800 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-aggregator
271c23f0f79e 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-l2gaspricer
4712391ae576 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-sequence-sender
dee4268e2bdc 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-sequencer
934870359c8d 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-eth-tx-manager
26cc9d84c5ee 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 14 minutes ago Exited (1) 14 minutes ago zkevm-sync
e25cdc601c0d 0xpolygon/cdk-validium-node:0.6.4-cdk.2 "/bin/sh -c '/app/zk…" 15 minutes ago Exited (1) 15 minutes ago
and logs says this
Version: 0.6.4+cdk.2
Git revision: 60a3e2e517c05535f5f9b175ca6064de0d2c4d83
Git branch: HEAD
Go version: go1.21.8
Built: 2024-04-01T13:21:52Z
OS/Arch: linux/amd64
2024-04-26T21:47:17.405Z INFO cmd/run.go:59 Starting application {"pid": 1, "version": "0.6.4+cdk.2"}
2024-04-26T21:47:17.444Z INFO db/db.go:121 Found 17 migrations as expected {"pid": 1, "version": "0.6.4+cdk.2"}
2024-04-26T21:47:17.512Z FATAL cmd/run.go:118 no contract code at given address
/home/runner/work/cdk-validium-node/cdk-validium-node/log/log.go:142 github.com/0xPolygonHermez/zkevm-node/log.appendStackTraceMaybeArgs()
/home/runner/work/cdk-validium-node/cdk-validium-node/log/log.go:223 github.com/0xPolygonHermez/zkevm-node/log.Fatal()
/home/runner/work/cdk-validium-node/cdk-validium-node/cmd/run.go:118 main.start()
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:277 github.com/urfave/cli/v2.(*Command).Run()
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:270 github.com/urfave/cli/v2.(*Command).Run()
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:335 github.com/urfave/cli/v2.(*App).RunContext()
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:309 github.com/urfave/cli/v2.(*App).Run()
/home/runner/work/cdk-validium-node/cdk-validium-node/cmd/main.go:198 main.main()
/opt/hostedtoolcache/go/1.21.8/x64/src/runtime/proc.go:267 runtime.main()
{"pid": 1, "version": "0.6.4+cdk.2"}
main.start
/home/runner/work/cdk-validium-node/cdk-validium-node/cmd/run.go:118
github.com/urfave/cli/v2.(*Command).Run
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:277
github.com/urfave/cli/v2.(*Command).Run
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:270
github.com/urfave/cli/v2.(*App).RunContext
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:335
github.com/urfave/cli/v2.(*App).Run
/home/runner/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:309
main.main
/home/runner/work/cdk-validium-node/cdk-validium-node/cmd/main.go:198
runtime.main
/opt/hostedtoolcache/go/1.21.8/x64/src/runtime/proc.go:267

all container failing also in previous image: hermeznetwork/cdk-validium-node:v0.0.3-RC2
rpc also not connected to brigde when connecting metamask as i mentioned above but bridge ui is accessable but now bridge ui show network error please provide any suggestions

[IvanWeber42]

Had the same issue on Ubuntu 22.04, it mysteriously does not happen on 24.04.

Not really a solution, but hopefully it helps you a little.

When checked out to previous commit the node start properly on both versions of OS.