#8 Can't login on new install of Halcyon

Closed
opened 5 years ago by freemo · 6 comments
freemo commented 5 years ago

I just installed halcyon and when i try to login I get the following error during authorization (the error is produced by my mastodon instance itself at https://qoto.org )

The redirect uri included is not valid.

I should point out when i use other halcyon servers to login to my instance it works fine, including the authorization. So it isn't likely related to my Mastodon setup.

My instance of halcyon is installed here: https://halcyon.qoto.org

my config.ini is as follows:

; Registar App Settings
[App]
api_client_name = Qoto
api_client_website = https://halcyon.qoto.org
who_to_follow_provider = https://vinayaka.distsn.org/cgi-bin/vinayaka-user-match-osa-api.cgi?{{host}}+{{user}}
I just installed halcyon and when i try to login I get the following error during authorization (the error is produced by my mastodon instance itself at https://qoto.org ) ``` The redirect uri included is not valid. ``` I should point out when i use other halcyon servers to login to my instance it works fine, including the authorization. So it isn't likely related to my Mastodon setup. My instance of halcyon is installed here: https://halcyon.qoto.org my config.ini is as follows: ``` ; Registar App Settings [App] api_client_name = Qoto api_client_website = https://halcyon.qoto.org who_to_follow_provider = https://vinayaka.distsn.org/cgi-bin/vinayaka-user-match-osa-api.cgi?{{host}}+{{user}} ```
Niklas Poslovski commented 5 years ago
Owner

Your instance works fine for me. Please remove the contents of your /data folder and try again. This error occurs if you have already tried it with an wrong config file. The server token for you instance with the wrong app settings is still saved in this case.

Your instance works fine for me. Please remove the contents of your /data folder and try again. This error occurs if you have already tried it with an wrong config file. The server token for you instance with the wrong app settings is still saved in this case.
freemo commented 5 years ago
Poster

Ok did that. Now i do get the authorization button. However when i click "authorize" it redirects me to a blank screen. If i start over i get the authorization request again.

Ok did that. Now i do get the authorization button. However when i click "authorize" it redirects me to a blank screen. If i start over i get the authorization request again.
Niklas Poslovski commented 5 years ago
Owner

I get the same problem now. Everytime I try to login to the instance I get another client_id token now. That means that the token requested from the Mastodon instance on the server side isn't stored and cannot be validated. Did you delete your /data directory? That could cause that problem. The /data directory must exist,it does only need to be empty at the beginning.

I get the same problem now. Everytime I try to login to the instance I get another client_id token now. That means that the token requested from the Mastodon instance on the server side isn't stored and cannot be validated. Did you delete your /data directory? That could cause that problem. The /data directory must exist,it does only need to be empty at the beginning.
freemo commented 5 years ago
Poster

That was it. It is working now, thanks.

That was it. It is working now, thanks.
freemo commented 5 years ago
Poster

By the way is there an easy way to restrict logins to only my domain and not other instances?

By the way is there an easy way to restrict logins to only my domain and not other instances?
Niklas Poslovski commented 5 years ago
Owner

Well,there isn't any officially supported option for that but it should work fine if you just chmod the /data directory to readonly for the php/nginx user. The file for your instance already exists if you've already used your instance and the chmod will prevent new files for other instances from beeing created.

Well,there isn't any officially supported option for that but it should work fine if you just chmod the /data directory to readonly for the php/nginx user. The file for your instance already exists if you've already used your instance and the chmod will prevent new files for other instances from beeing created.
Sign in to join this conversation.
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.