You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wrapping my head for a while now around the problem of connecting to the NATS cluster from inside the NatsBox pod after I configured the JWT resolver.
I think the configuration is ok, setting the operator, system_account and resolver_preload. The server seems to start ok also:
Starting nats-server
Version: 2.10.23
Git: [145e44d]
Cluster: wide-stack-nats
Name: wide-stack-nats-2
Node: AacsVtx5
ID: NB5JXNEYBFEAREOHW4X7NUTY6C4SX2R6H2GDO6TWQXSVVS7VXCG
Using configuration file: /etc/nats-config/nats.conf
Trusted Operators
System : ""
Operator: "wide"
Issued : 2024-12-23 15:29:48 +0000 UTC
Expires : Never
Starting http monitor on 0.0.0.0:8222
Managing all jwt in exclusive directory /data/resolver
Starting JetStream
_ ___ _____ ___ _____ ___ ___ _ __ __
_ | | __|_ _/ __|_ _| _ \ __| /_\ | \/ |
| || | _| | | \__ \ | | | / _| / _ \| |\/| |
\__/|___| |_| |___/ |_| |_|_\___/_/ \_\_| |_|
[6] 2024/12/24 09:46:23.791262 [INF]
https://docs.nats.io/jetstream
[6] 2024/12/24 09:46:23.791264 [INF]
---------------- JETSTREAM ----------------
Max Memory: 0 B
Max Storage: 10.00 GB
Store Directory: "/data/jetstream"
-------------------------------------------
Account fetch failed: will only fetch valid account keys
Starting JetStream cluster
Creating JetStream metadata controller
JetStream cluster recovering state
Listening for MQTT clients on mqtt://0.0.0.0:1883
Listening for client connections on 0.0.0.0:4222
Server is ready
Cluster name is wide-stack-nats
Listening for route connections on 0.0.0.0:6222
From inside the NatsBox pod:
Account Information
User: UBN5HLF4LXGWGO7DMLB2IJ6CMVAPJXXMJF7TS6VVTI43SKZ25I4SM4D4
Account: ADJ3DFXMU2FRIFCLHOOLUYABGCFR5D5UKGEI5G7NJJLMYNB4OB3S4T2W
Expires: never
Client ID: 45
Client IP: 10.42.0.2
RTT: 70µs
Headers Supported: true
Maximum Payload: 1.0 MiB
Connected Cluster: wide-stack-nats
Connected URL: nats://wide-stack-nats:4222
Connected Address: 10.43.30.48:4222
Connected Server ID: NB5JXNEYBFEAREOHW4X7NUTY6C4SX2R6H2GDO6TWQXSVVS7VXCGEDTIO
Connected Server Version: 2.10.23
Connected Server Name: wide-stack-nats-2
TLS Connection: no
Could not obtain account information: JetStream not enabled for account (10039)
When I try to add an account:
# nsc add account test_account
Error: set an operator -- 'nsc env -o operatorName'
And when I try to set the operator:
~ # nsc env -o wide
Error: operator "wide" not in `/nsc/nats/nsc/stores`
How can I make sure the NatsBox knows about the operator?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm wrapping my head for a while now around the problem of connecting to the NATS cluster from inside the NatsBox pod after I configured the JWT resolver.
I think the configuration is ok, setting the operator, system_account and resolver_preload. The server seems to start ok also:
From inside the NatsBox pod:
When I try to add an account:
And when I try to set the operator:
How can I make sure the NatsBox knows about the operator?
Beta Was this translation helpful? Give feedback.
All reactions