I just created my own GoToSocial instance and it seems I can’t connect to it. Right after I enter the host name, I get
Invalid Mastodon server
How do I connect to my custom instance?
Found this setting on GTS, but even changing to true didn’t help:
# Bool. This flag will inject a Mastodon version into the version field that
# is included in /api/v1/instance. This version is often used by Mastodon clients
# to do API feature detection. By injecting a Mastodon compatible version, it is
# possible to cajole those clients to behave correctly with GoToSocial.
#
# Options: [true, false]
# Default: false
instance-inject-mastodon-version: true
Found this topic
Will try to get listed on instances.social and see how it goes
Looks like instances.social is a dead project. There are a year old not addressed issues about instances not being added. My instance is also already more than 24h old, but I can’t add it. There’s no point even creating an issue with them.
Since botsin.space is closing and most instances are quite strict about bot accounts, is there any other way I could connect my own instance to Trakt?
cc: @justin
Some more time passed and now I’m getting this error on instances.social:
Sign up failed. It looks like this instance is not a Mastodon or Pleroma instance. Other fediverse instances can show up on instances.social but are not (yet) compatible with this admin space.
But I believe GoToSocial should be fully compatible with the Mastodon API. It would be really sad if I couldn’t connect Trakt to my instance
It would be really great to get some advice rather sooner than later. Lately botsin.space just timeouts (I assume one of the reasons to shut it down), so most of the time Trakt activity simply doesn’t go through. And also I’d still need to migrate the bot account to my instance. I wouldn’t want to leave it for the last day 
So a few days ago I decided to check instances.social once more and I don’t know what changed, but registration went through. After a day (as instructed) I tried to connect it here on Trakt, but still didn’t work. Then I realized maybe because I marked it to be hidden from instances picker, so I changed this option. Now two more days have passed and I still can’t connect it to Trakt
Any ideas, @justin?
@Karmalakas What is the instance name so I can check what Trakt has cached?
It’s social.karmalakas.lt
When I filter for it on instances.social, it’s not there, although I can login there and change settings for days now
I’m not able to connect to social.karmalakas.lt, it just times out. Is the instance publicly accessible?
It is. I wouldn’t be able to register it without outside access. I even have a test follwer from mastodon.social 
And I can open it in incognito tab only using mobile data (screenshot is not incognito, because it doesn’t allow the capture)
BTW, GoToSocial returns a 418 HTTP error if request doesn’t have a User Agent header, so not sure if that might be the issue (found out this only today)
I manually added your server to Trakt. Please try connecting now (in Trakt settings) and I believe it will auto create the necessary OAuth app and connection.
So I click connect, enter my instance, on instance page I enter login credentials, on app confirmation I authorize Trakt and when redirected back here I get a notification “invalid credentials”
Tried also in incognito, thought maybe something’s messing up with my other account, but same result. Will try tomorrow morning to check the callback url when I’m at my PC
It’s all handled server side, so the browser likely won’t matter. There isn’t much else I can do if it’s not working unfortunately.
So callback seems fine
https://trakt.tv/auth/auth/mastodon/callback?code=MZY...2JM&state=584...f01
I just tried logging out and re-authorizing on different apps - Tusky (Android app), fe.soapbox.pub (web app) and even downloaded some new Whalebird (Windows desktop app) and all of them authorized just fine. Whalebird required manual code entry, but it authorized without any problem 
Started playing around and I see that some requests on my GTS instance behave a bit strange. I’ll try contacting the GTS support. Thanks for now for your time to look into this and adding the domain 
I’ll get back when I find something
I tried debugging, but there are no logs on my side. Raised an issue on the GTS project and one of the GTS maintainers replied:
Hiya, if GtS is redirecting you back to the app’s redirect_uri then there won’t be any helpful logs because as far as GoToSocial is concerned, everything works as expected. Maybe trakt.tv doesn’t like something about the code or state that’s being provided in the query parameters, but I’ve no clue what it might be objecting to, or why. Is that an open source project, do you know? If so we could just have a look at the code for handling callbacks and see what it’s trying to do.
Is there any chance to see some underlying cause what gives the “Invalid credentials” error? As I mentioned, every other app I tried (I think it’s at least 5 now of different types) authorizes without any issues
If you’re up to it, I’m willing to get on a call to help debug. Or I could create a temporary account on my instance and send you credentials 