Newt throws errors trying to install as binary in Debian 12 - [Failed to connect: failed to get token with status code 400] #587

New Issue

2025-11-13T12:05:13-06:00

GiteaMirror commented

2025-11-13 12:05:13 -06:00

Originally created by @SprMario on GitHub (Aug 16, 2025).

Hi all,

Here I am again! It seems I am hitting the lottery with Pangolin. I hope MorganKryze doesn't see this 😶‍🌫️ .

Today I wanted to replace Newt in docker with Newt as a binary for the performance gains, at least I think Docker can introduce some overhead.
Following this guide: https://docs.digpangolin.com/manage/sites/install-site

Environment:
Proxmox VM running Debian 12

The steps to install are done without any issues(binary buick install) but when I try to start newt with my information following the guide and using my information, I get errors.

Command:
newt \ --id 31frd0uzbjvp721 \ --secret h51mmlknrvrwv8s4r1i210azhumt6isgbpyavxodibx1k2d6 \ --endpoint https://example.com

These credentials are generated by Pangolin dashboard once you try to create a site. The dashboard is reachable and works as expected(thanks Morgan).

I also tried to run Newt through a system service file. Using the example of the guide in the correct path I made sure the service did NOT run using htop.

Then reloaded the daemon:
systemctl daemon-reload

Enabled the service
systemctl enable newt.service

Then start the service file with
systemctl start newt.service

No errors unless I do:
systemctl status newt.service

Output:

Does anyone know what I can do?

Originally created by @SprMario on GitHub (Aug 16, 2025). Hi all, Here I am again! It seems I am hitting the lottery with Pangolin. I hope MorganKryze doesn't see this 😶‍🌫️ . Today I wanted to replace Newt in docker with Newt as a binary for the performance gains, at least I think Docker can introduce some overhead. Following this guide: https://docs.digpangolin.com/manage/sites/install-site Environment: Proxmox VM running Debian 12 The steps to install are done without any issues(binary buick install) but when I try to start newt with my information following the guide and using my information, I get errors. Command: `newt \ --id 31frd0uzbjvp721 \ --secret h51mmlknrvrwv8s4r1i210azhumt6isgbpyavxodibx1k2d6 \ --endpoint https://example.com` These credentials are generated by Pangolin dashboard once you try to create a site. The dashboard is reachable and works as expected(thanks Morgan). <img width="904" height="96" alt="Image" src="https://github.com/user-attachments/assets/2b7f1e09-69de-4cd3-a12a-3568a48bd884" /> I also tried to run Newt through a system service file. Using the example of the guide in the correct path I made sure the service did NOT run using htop. Then reloaded the daemon: `systemctl daemon-reload` Enabled the service `systemctl enable newt.service` Then start the service file with `systemctl start newt.service` No errors unless I do: `systemctl status newt.service` Output: <img width="1381" height="294" alt="Image" src="https://github.com/user-attachments/assets/b0fa40b6-411d-4a78-9773-150db7608d42" /> Does anyone know what I can do?

GiteaMirror closed this issue

2025-11-13 12:05:13 -06:00

GiteaMirror commented

2025-11-13 12:05:13 -06:00

@oschwartz10612 commented on GitHub (Aug 17, 2025):

Hum I don't see a reason it should not work. 400 is a bad request but
your command looks good. If you turn on --log-level debug in newt does
that show you anything?

Also could be good to look in Pangolin logs. See any errors?

IDK why you would get a 400 and not a 403 - I would expect if the id or
secret were wrong but check that as well to make sure they are correct.

LMK what you find.

@oschwartz10612 commented on GitHub (Aug 17, 2025): Hum I don't see a reason it should not work. 400 is a bad request but your command looks good. If you turn on --log-level debug in newt does that show you anything? Also could be good to look in Pangolin logs. See any errors? IDK why you would get a 400 and not a 403 - I would expect if the id or secret were wrong but check that as well to make sure they are correct. LMK what you find.

GiteaMirror commented

2025-11-13 12:05:13 -06:00

@SprMario commented on GitHub (Aug 17, 2025):

Hum I don't see a reason it should not work. 400 is a bad request but
your command looks good. If you turn on --log-level debug in newt does
that show you anything?

Also could be good to look in Pangolin logs. See any errors?

IDK why you would get a 400 and not a 403 - I would expect if the id or
secret were wrong but check that as well to make sure they are correct.

LMK what you find.

Output of Newt with log-level debug:

It seems that it doesn't reach my endpoint at all, there are no logs on Pangolin side.

@SprMario commented on GitHub (Aug 17, 2025): > Hum I don't see a reason it should not work. 400 is a bad request but > your command looks good. If you turn on --log-level debug in newt does > that show you anything? > > Also could be good to look in Pangolin logs. See any errors? > > IDK why you would get a 400 and not a 403 - I would expect if the id or > secret were wrong but check that as well to make sure they are correct. > > LMK what you find. Output of Newt with log-level debug: <img width="900" height="216" alt="Image" src="https://github.com/user-attachments/assets/2efa43a7-1f40-4a4b-9c98-683a85f24061" /> It seems that it doesn't reach my endpoint at all, there are no logs on Pangolin side.

GiteaMirror commented

2025-11-13 12:05:14 -06:00

@SprMario commented on GitHub (Aug 18, 2025):

Going to start from scratch. This issue seems too new for the community as I am barely able to find results on the errors messages.

@SprMario commented on GitHub (Aug 18, 2025): Going to start from scratch. This issue seems too new for the community as I am barely able to find results on the errors messages.

GiteaMirror commented

2025-11-13 12:05:14 -06:00

@oschwartz10612 commented on GitHub (Aug 23, 2025):

Hi!

Sorry for the delays!

Okay if you moved on. Just a thought here it looks like there is
https:// in the endpoint print out which is not usually the case but I
could be fooling myself. How was the endpoint entered into the command?

Its closed so if you are good feel free to ignore.

@oschwartz10612 commented on GitHub (Aug 23, 2025): Hi! Sorry for the delays! Okay if you moved on. Just a thought here it looks like there is https:// in the endpoint print out which is not usually the case but I could be fooling myself. How was the endpoint entered into the command? Its closed so if you are good feel free to ignore.

GiteaMirror commented

2025-11-13 12:05:14 -06:00

@SprMario commented on GitHub (Aug 23, 2025):

Hi!

Sorry for the delays!

Okay if you moved on. Just a thought here it looks like there is
https:// in the endpoint print out which is not usually the case but I
could be fooling myself. How was the endpoint entered into the command?

Its closed so if you are good feel free to ignore.

Hello,

The example is from the website which i followed quite closely and after reinstalling I used HTTPS too. I don't think that was the issue.

@SprMario commented on GitHub (Aug 23, 2025): > Hi! > > Sorry for the delays! > > Okay if you moved on. Just a thought here it looks like there is > https:// in the endpoint print out which is not usually the case but I > could be fooling myself. How was the endpoint entered into the command? > > Its closed so if you are good feel free to ignore. Hello, The example is from the website which i followed quite closely and after reinstalling I used HTTPS too. I don't think that was the issue.