-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cURL issue #45
Comments
Hi, it seems like you're running each line individually rather than running them in a single command. Can you send the full interaction (input and output) from your console? Also, I noticed that I forgot to update the commands.json file in a while. I might just make this process a little easier overall and remove the requirement to send a request manually. |
|
Hi! Could you try the new hosting instructions? I've hopefully made it easier to update the slash commands and everything is up to date now, too. You can find everything in the README. |
On this command there is an extra ` make sure to remove it
|
I am also having the problem
I have had this waiting for 2 hours and the bot is not online, the webserver is not up and the bot will not respond to commands. |
There is no warning/error message indicated here. Have you set up the interactions endpoint in the developer portal? How do you test if the web server is up? |
I fixed it, I added the extended port in the docker compose file and that fixed the problem. You might want to put this in the docker compose file from the start .
|
It says that the host port will be picked by Docker by default and that you have to change this if you have a specific port you want to use. I don't want to impose a specific port on users, but I suppose I could give a default |
When I try and publish the commands, I get the error
I have the token and app id set, I am wondering if it has something to do with the
-H "Authorization: Bot $token" \
part because it says its on line 3.Does anyone else have this issue and any idea on how to solve it.
Thanks.
The text was updated successfully, but these errors were encountered: