Just installed Auto Scheduler but cannot schedule more than a single-pass as error given … ‘detail’: Invalid token header. No credentials provided.
@m0roj this error says that you haven’t included a header with the API key in the headers of the request.
Just in case, have you followed the configuration step in librespacefoundation / SatNOGS / satnogs-auto-scheduler · GitLab? If yes please make sure that the API key in .env file is the same as the one you see in SatNOGS Network.
Thank you @fredy - problem solved.
Cause: a couple of code typos.
Scheduler working fine now, but a better LNA and BPF needed for VHF data decodes.
Any particular recommendations please?
1 Like
Hi Fredy.
Can you clarify this statement for me as I’m unable to get the satnogs-auto-scheduler running and I’m having the same issues as the gent before.
Where is the file .env located as all i can find is a folder called env but NOT the file.
I’ve been able to edit the env-dist file and add the API key but I’m still having no luck.
If yes please make sure that the API key in .env file is the same as the one you see in SatNOGS Network.
Thanks
Karl.
So i think I’ve figured it out in that.
I’ve edited the “env-dist” file and added my API Token then i had to save the file with the extension .env so ending up with “env-dist.env” and now all seems to work.
This is worded very strange to me.
(Copy the env-dist file to .env and edit this file to add your SatNOGS Network API token.)
And should read.
(Edit the env-dist file to add your SatNOGS Network API token and then save it with the extension .env
so it resembles env-dist.env)
Please correct me if I’m wrong.
Thanks
Karl.
1 Like
Hi, I think this is what is going on.
In my setup the .env file is in the same directory as the satnogs-auto-scheduler directory.
The .env file on Linux (Pi) systems is a “hidden” file, since it starts with a dot. So the file may be somewhere like (depending where you git cloned): /home/pi/satnogs-auto-scheduler/.env
That file is ignored by git, as you can see it listed in .gitignore. There wouldn’t be a satnogs-auto-scheduler/.env directory when you cloned, so perhaps that got inadvertantly created. If so, you can just remove that .env directory and replace it with an .env file with the appropriate API info.
If it is working with the file env-dist.env that is probably more coincidence than anything, it is probably parsing all the .env files in the directory (speculating on that).
I hope I’m somewhat right and this helps.
Happy hacking.
3 Likes
Exactly!
The env syllable appears in multiple different contexts here:
-
.envis the filename of the configuration file. When cloning the repository it doesn’t exists at first, and the user is supposed to create it (based on the template, seeenv-dist) -
env-distis the template for the configuration file. -
envis most probably a folder created by python-virtualenv which contains a Python Virtual Environment
Those names are common when deploying services written in Python, but I agree that for new users with less experience they can be extremely confusing.
2 Likes
I migrated the Satnogs station with the Bullseye image and after configuring and running it, I installed Auto-Scheduler.
I configured the .env file, with the API Key of my station and I still have the error "Reason: {‘detail’: ‘Invalid token header. No credentials provided.’}, I can’t find what the error could be. I have activated the different log levels and none have helped me discover the error.
Can anyone give me some help to find the problem? Thank you so much.