After installing pyMC_console, dashboard requires authentication, but no place to add it in yaml file #65

New Issue

2026-10-27T09:31:03+01:00

adam commented

2026-10-27 09:31:03 +01:00

Sent to ask here by @Treehouse who wants to defer to @rightup ...

After successfully installing pymc_console on top of a working pyMC_Repeater install, the web dashboard now requires authentication.

Reviewing the /etc/pymc_repeater/config.yaml file doesn't show any obvious place to add the user/pass. Not clear on how to proceed.

Sent to ask here by @Treehouse who wants to defer to @rightup ... After successfully installing pymc_console on top of a working pyMC_Repeater install, the web dashboard now requires authentication. Reviewing the /etc/pymc_repeater/config.yaml file doesn't show any obvious place to add the user/pass. Not clear on how to proceed.

adam closed this issue

2026-10-27 09:31:03 +01:00

adam commented

2026-10-27 09:31:04 +01:00

Does it have a jwt key in your config? The password should be in the repeater section.

Does it have a jwt key in your config? The password should be in the repeater section.

adam commented

2026-10-27 09:31:05 +01:00

I had a similar issue first time I set it up but did it all again and was great. I must have missed something On 22 Mar 2026, at 20:13, Lloyd @.***> wrote:rightup left a comment (rightup/pyMC_Repeater#156)
Does it have a jwt key in your config? The password should be in the repeater section.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I had a similar issue first time I set it up but did it all again and was great. I must have missed something On 22 Mar 2026, at 20:13, Lloyd ***@***.***> wrote:rightup left a comment (rightup/pyMC_Repeater#156) Does it have a jwt key in your config? The password should be in the repeater section. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

adam commented

2026-10-27 09:31:05 +01:00

Does it have a jwt key in your config? The password should be in the repeater section.

Here's what's in the repeater section of the yaml...

repeater:
  # Node name for logging and identification
  node_name: "N6WK pyMC Repeater"
  # Geographic location (optional)
  # Latitude in decimal degrees (-90 to 90)
  latitude: 34.44292
  # Longitude in decimal degrees (-180 to 180)
  longitude: -119.72136
  # Path to identity file (public/private key)
  # If not specified, a new identity will be generated
  identity_file: null
  # Duplicate packet cache TTL in seconds
  cache_ttl: 60
  # Score-based transmission filtering
  # Enable quality-based packet filtering and adaptive delays
  use_score_for_tx: false
  # Score threshold for quality monitoring (future use)
  # Currently reserved for potential future features like dashboard alerts,
  # proactive statistics collection, or advanced filtering strategies.
  # Changing this value has no effect on current packet processing.
  score_threshold: 0.3
  # Automatic advertisement interval in hours
  # The repeater will send an advertisement packet at this interval
  # Set to 0 to disable automatic adverts (manual only via web interface)
  # Range: 0 (disabled) to 24+ hours
  # Recommended: 10 hours for typical deployments
  send_advert_interval_hours: 48
  # Respond to discovery requests from other nodes
  # When enabled, the repeater will automatically respond to discovery packets
  # with its node information (node type 2 - repeater)
  allow_discovery: true

> Does it have a jwt key in your config? The password should be in the repeater section. Here's what's in the repeater section of the yaml... ``` repeater: # Node name for logging and identification node_name: "N6WK pyMC Repeater" # Geographic location (optional) # Latitude in decimal degrees (-90 to 90) latitude: 34.44292 # Longitude in decimal degrees (-180 to 180) longitude: -119.72136 # Path to identity file (public/private key) # If not specified, a new identity will be generated identity_file: null # Duplicate packet cache TTL in seconds cache_ttl: 60 # Score-based transmission filtering # Enable quality-based packet filtering and adaptive delays use_score_for_tx: false # Score threshold for quality monitoring (future use) # Currently reserved for potential future features like dashboard alerts, # proactive statistics collection, or advanced filtering strategies. # Changing this value has no effect on current packet processing. score_threshold: 0.3 # Automatic advertisement interval in hours # The repeater will send an advertisement packet at this interval # Set to 0 to disable automatic adverts (manual only via web interface) # Range: 0 (disabled) to 24+ hours # Recommended: 10 hours for typical deployments send_advert_interval_hours: 48 # Respond to discovery requests from other nodes # When enabled, the repeater will automatically respond to discovery packets # with its node information (node type 2 - repeater) allow_discovery: true ```

adam commented

2026-10-27 09:31:06 +01:00

Check out the example config seems you are missing some bits

https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example

Check out the example config seems you are missing some bits https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example

adam commented

2026-10-27 09:31:06 +01:00

Check out the example config seems you are missing some bits

https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example

Amazing, thank you. It’s worth noting in terms of this issue that I neither added nor deleted anything to that yaml file, I only changed the default values appropriately.

The config.yaml.example file installed in the /pyMC_Repeater directory also lacks those fields.

> Check out the example config seems you are missing some bits > > https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example Amazing, thank you. It’s worth noting in terms of this issue that I neither added nor deleted anything to that yaml file, I only changed the default values appropriately. The config.yaml.example file installed in the /pyMC_Repeater directory also lacks those fields.

adam commented

2026-10-27 09:31:07 +01:00

Interesting what branch do you have installed?

Interesting what branch do you have installed?

adam commented

2026-10-27 09:31:08 +01:00

It’s whatever is chosen by default when you invoke “git clone https://github.com/rightup/pyMC_Repeater.git”

It’s whatever is chosen by default when you invoke “git clone https://github.com/rightup/pyMC_Repeater.git”

adam commented

2026-10-27 09:31:08 +01:00

You don't need to edit the yaml file. You set it up with manage.shOn 22 Mar 2026, at 20:38, porkrind @.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#156)

Check out the example config seems you are missing some bits
https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example

Amazing, thank you. It’s worth noting in terms of this issue that I neither added nor deleted anything to that yaml file, I only changed the default values appropriately.
The config.yaml.example file installed in the /pyMC_Repeater directory also lacks those fields.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

You don't need to edit the yaml file. You set it up with manage.shOn 22 Mar 2026, at 20:38, porkrind ***@***.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#156) Check out the example config seems you are missing some bits https://github.com/rightup/pyMC_Repeater/blob/dev/config.yaml.example Amazing, thank you. It’s worth noting in terms of this issue that I neither added nor deleted anything to that yaml file, I only changed the default values appropriately. The config.yaml.example file installed in the /pyMC_Repeater directory also lacks those fields. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

adam commented

2026-10-27 09:31:09 +01:00

You don't need to edit the yaml file. You set it up with manage.sh

I don’t see any way around editing the yaml file…

Invoking “config” from manage.sh doesn’t ask to set an admin password
The available radio configurations available in the config setting do not encompass the settings we use in SoCal.

> You don't need to edit the yaml file. You set it up with manage.sh I don’t see any way around editing the yaml file… 1. Invoking “config” from manage.sh doesn’t ask to set an admin password 2. The available radio configurations available in the config setting do not encompass the settings we use in SoCal.

adam commented

2026-10-27 09:31:09 +01:00

Try a fresh install from the newRadios branch.

If you like to live dangerously, you can always give feat/companion a go ;)

Try a fresh install from the newRadios branch. If you like to live dangerously, you can always give feat/companion a go ;)

adam commented

2026-10-27 09:31:10 +01:00

No it doesn't but one setup by that it tells you to open the url and first log in you set it up there. On 22 Mar 2026, at 20:58, porkrind @.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#156)

You don't need to edit the yaml file. You set it up with manage.sh

I don’t see any way around editing the yaml file…

Invoking “config” from manage.sh doesn’t ask to set an admin password
The available radio configurations available in the config setting do not encompass the settings we use in SoCal.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

No it doesn't but one setup by that it tells you to open the url and first log in you set it up there. On 22 Mar 2026, at 20:58, porkrind ***@***.***> wrote:porkrind left a comment (rightup/pyMC_Repeater#156) You don't need to edit the yaml file. You set it up with manage.sh I don’t see any way around editing the yaml file… Invoking “config” from manage.sh doesn’t ask to set an admin password The available radio configurations available in the config setting do not encompass the settings we use in SoCal. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

adam commented

2026-10-27 09:31:10 +01:00

bugfix: committed to 7bcab773dd (companion branch)

bugfix: committed to 7bcab773ddcbcf84ad3d0ab868a4af6d31468d51 (companion branch)

adam commented

2026-10-27 09:31:11 +01:00

You don't add it. You set it up when you run ./manage.shOn 24 Mar 2026, at 11:11, Lloyd @.***> wrote:rightup left a comment (rightup/pyMC_Repeater#156)
bugfix: committed to 7bcab77 (companion branch)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

You don't add it. You set it up when you run ./manage.shOn 24 Mar 2026, at 11:11, Lloyd ***@***.***> wrote:rightup left a comment (rightup/pyMC_Repeater#156) bugfix: committed to 7bcab77 (companion branch) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#65