SeAT - ❓-support - Page 16

I know that you really want to use this plugin but I would recommend wait for release 😛

haha okay I am looking forward to using it because it seems like it has a lot of features that will be super useful! But I will wait.

It is end to end process that doesnt stop on recruiting. But connector with its current permission model is a pain to hook up thats why plugin is not ready yet to be used.

Ah yeah but atm

I have removed the plugin for now :(

Yes.. and the meaning of unrelease means it is NOT finished.. it like eating a half baked cookie.. you will get a nice stomach ache if you eat it raw... So just wait and let Matt finish it.. dont break his concentration and he might be able to deliver a release faster..

Yeah I know I got a bit excited

I know what dev branch means so I didnt move any corp infra onto it

but I was kinda hoping it worked since I liked the feature set

I know.. I cant waiting for his other plugins to be release.. but i have to wait.. patiently.........

we wait

We need to clone him!!

@user_106453105427640320 ok i got the pap system to work, but i cant get the discord bot to post.

tho when i click the notifcation button it works

what tags are you doing on the calander event? on my discord I have to make sure corp fleet is tagged or it won't ping

but it's a corp seat for a corp discord so that doesn't really matter on my end

mines also a corp seat for a corp discord

i put all the tags on it

o7 Im using the docker compose way of running SeAT https://eveseat.github.io/docs/installation/docker_installation/ Im seeing 4 out of the 6 SeAT Module Versions (core) that are out of date. However I am unsure on how to update these. I have tried running composer install and composer update --no-dev inside the worker container's bash shell, but that did not update these packages. I am out of ideas and do not see anything about updating SeAT Module Versions in the documentation. Could someone direct me on how to proceed or help me out? thnx

Upgrade instructions should cover that

Alright, good to know that I am in the right direction. I'll proceed with following the upgrade instructions. thank you

Just to be clear, you should be following the upgrade instructions for docker, which do not directly interact with composer https://eveseat.github.io/docs/upgrading/general/#docker-installation

does anyone use the teamspeak connector? I'm surprised to see it doesnt enforce usernames like the discord connector does

Ah yeah turns out it can’t

https://github.com/zenobio93/seat-teamspeak/pull/1 well here’s a pr that at least makes it work like allianceauth

heh... we ran a custom ts3 auth thing before, we kept the 'spider' that checks that no one changes their username

I worked up a poc that uses the team speak access key to join them to a single use group instead of relying on the name at all. This also allows you to set a ts server password that you never have to give out

It works pretty well, but Couldnt figure out how to port that functionaility into seat

Need thoughts on why this is failing

logs are killing my server

curl works to endpoints too

from host and container

Analytics always fails for everyone at the moment. They shouldn't be high volume though. Also based on the time durations, they are a symptom not the cause. Is your queue overloaded? Does it ever get to 0? My assumption on the logs you haven't provided is that the error is MaxAttemptsExceeded

que doesnt seem overloaded at all

dont see in the logs MaxAttemptsExceeded

looking at raw logs seeing

[2026-07-03 14:53:47] local.ERROR: cURL error 6: Could not resolve host: www.google-analytics.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.google-analytics.com/collect?v=1&tid=UA-80887494-1&cid=96a80053-1e76-493b-b72f-17bf71c4c5ca&t=exception&aip=1&an=SeAT&av=api%2F5.0.1%2C%20eseye%2F3.2.1%2C%20eveapi%2F5.0.35%2C%20notifications%2F5.0.16%2C%20services%2F5.1.0%2C%20web%2F5.0.35&ua=SeAT%2FLinux%2F6.8.0-134-generic%2Fx86_64&z=897&exd=Illuminate%5CQueue%5CMaxAttemptsExceededException%3ASeat%5CEveapi%5CJobs%5CToken%5CRefreshAccessToken%20has%20been%20attempted%20too%20many%20times.&exf=1 {"exception":"[object] (GuzzleHttp\\Exception\\ConnectException(code: 0): cURL error 6: Could not resolve host: www.google-analytics.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.google-analytics.com/collect?v=1&tid=UA-80887494-1&cid=96a80053-1e76-493b-b72f-17bf71c4c5ca&t=exception&aip=1&an=SeAT&av=api%2F5.0.1%2C%20eseye%2F3.2.1%2C%20eveapi%2F5.0.35%2C%20notifications%2F5.0.16%2C%20services%2F5.1.0%2C%20web%2F5.0.35&ua=SeAT%2FLinux%2F6.8.0-134-generic%2Fx86_64&z=897&exd=Illuminate%5CQueue%5CMaxAttemptsExceededException%3ASeat%5CEveapi%5CJobs%5CToken%5CRefreshAccessToken%20has%20been%20attempted%20too%20many%20times.&exf=1 at /var/www/seat/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:277)
[2026-07-03 15:03:54] local.ERROR: Seat\Eveapi\Jobs\Token\RefreshAccessToken has been attempted too many times. {"exception":"[object] (Illuminate\\Queue\\MaxAttemptsExceededException(code: 0): Seat\\Eveapi\\Jobs\\Token\\RefreshAccessToken has been attempted too many times. at /var/www/seat/vendor/laravel/framework/src/Illuminate/Queue/MaxAttemptsExceededException.php:24)
#0 /var/www/seat/vendor/laravel/framework/src/Illuminate/Queue/Worker.php(785): Illuminate\\Queue\\MaxAttemptsExceededException::forJob(Object(Illuminate\\Queue\\Jobs\\RedisJob))

so guess its refreshtokens having issues ?

yeah it is

Is your instance up to date?

Its i think 2 versions of container behind.

All the packages though say up to date

@user_301981661761896449 do we have an appetite for implementing something into notifications that prevents duplicate notifications from being sent (for example, an attack notification that goes to all members of the corp, and if the corp is selected as "affiliation", not having it ping identically for every single character in that corp)? i can work on implementing it in a PR, i was just curious if this was an intentional action and would be rejected or if it would be acceptable. I ask because I have some ideas for plugins but the current notification system hurts some implmentability and I would have to recreate custom notifications to do so which i dont want to do for obvious reasons.

(also: https://github.com/eveseat/notifications/pull/116)

you could setup a squad that the notifications go out to, that has a requirement to have one of the other groups, like corp member, affiliate, camper, old fart.

that way it only sends the notification to the notification group which contains the others

For the discord connector... I used warlof/seat-discord-connector since zenobio was giving me errors about incompatible versions Warlof connector works except that it seems to want full control over every role? I honestly only want it to assign the member role

It keeps erroring trying to remove the "Member" set when all I want is for it to assign a role if someone is in a corp

I dont see why it keeps trying to remove set member that set doesnt even exist as something I made

Thats expected...it is built to control all the roles and all members on the server

It basically has a list of users, and the discord roles it thinks the user should have...and then it tries to remove the rest

Any good ways to see what Refresh tokens are causing issues and how to delete just the ones causing issues, my logs growth keeps killing my server @user_398925835794645002

Get some log snippet? There are multiple kinds of refresh token issue, some of them leads to automatic removal

log gives No indication as to which or what refresh token issue

redis log is just refresh token issue

looks like DNS problem

check your internet

not dns or internet problem

can easily ping / curl from container or host

That is the error shown here..

[2026-07-15 21:05:21] local.ERROR: cURL error 6: Could not resolve host: login.eveonline.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://login.eveonline.com/v2/oauth/token

When to check on https://evestatus.com/ to see if there was a blip but unfortunately, the site is down....

I dont know if the constrainers need an update, or maybe Cloudflare blocked your IP..

is the connector broken?

command works in terminal but buttons in UI settings throw this error.

thats only part of the error , the rest of the error exp when looking at redis que shows refresh token

my guess is thiers an issue with the gaining new tokens

nah some exercise is needed to look at the error correctly...especially about what to ignore

that works in similar way as springboot where you get huge stack traces.

they eventually leads back to Curl, and then the DNS problem

Cloudflare blocking IPs does not look like this I think

Well curl / dns problem is ruled out

So leads back to refresh token ans since redis is also saying refresh token error

I found the issue ... Eseye is still using esi.evetech.net which no longer works

still a couple other spots using the old url which is making my logs full

so this is probally happening to more people then just me

It is not a wrong URL because only / receives the redirect

See https://esi.evetech.net/characters/2114299824

and thats the url the error is saying its failing to connect to ...

You didnt publish that log

shouldnt that be https:// ? not https:/

these days they act the same way

and give the same response