SeAT - ❓-support - Page 15

@user_301981661761896449 Should i be searching for "fitting" in the laravel logs? the log is below.

@user_301981661761896449 network ☝️

Have a look at what the response was on the requests that were 500 status

like this?

ahh this

Yep this panel, but click the response tab

that...looks unhelpful. sorry...

Haha all good.. I'll have to have a look later at the log file you sent as should be in there, I am just out atm.

no worries and no pressure take your time and Happy Holidays!!

All good. Can you DM me the fit please

It's all fits....

none of the fits i have on there show me the character column

but here is the first one i have on there

[Vexor, SOLOS Vexor - Angel Ratting (Fleet)]
Omnidirectional Tracking Enhancer II
Drone Damage Amplifier II
Drone Damage Amplifier II
Drone Damage Amplifier II
Damage Control II

100MN Monopropellant Enduring Afterburner
Large Shield Extender II
Large Shield Extender II
Pithum A-Type Explosive Shield Amplifier

Drone Link Augmentor II
Auto Targeting System I
125mm Gatling AutoCannon I



Medium Core Defense Field Extender I
Medium Core Defense Field Extender I
Medium Core Defense Field Extender I

Warrior II x5
Republic Fleet Warrior x1
Republic Fleet Valkyrie x2
Hornet EC-300 x5
Republic Fleet Berserker x2

Republic Fleet Fusion S x200

@user_301981661761896449 ☝️

Hmm interesting... I thought it might have been on fits with a new item. As the error is to do with the SDE (which currently has not kept up with eve) I'll look into it more later

Ive had the same issue for a while, but only on accounts that were assigned admin permissions. Meanwhile logging in as admin through the link generated in the command line shows it just fine.

@user_301981661761896449 https://github.com/eveseat-plugins/seat-fitting/pull/20 Please double check but this should fix the errors + added search functionality in fitting.blade.php by ship type and fit name

Running on Ubuntu in a docker instance - and after patching running into some errors with traefik.

2025-12-21T22:44:50Z ERR Provider error, retrying in 5.000492591s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=docker

anyone else seeing these?

https://discord.com/channels/821361165791133716/821363152046129193/1445022759905267883

https://tenor.com/view/are-we-there-yet-deadpool-gif-5676800

Happy Holidays to all! I recently came upon an error with my SeAT setup, and haven't been able to track it down yet. After installing several plugins (PI, HR, Production, Structure manager), whenever anyone goes to the skills tab, we recieve a server 500 error. Any troubleshooting help would be appreciated.

Check your logs and post them here

.docs.troubleshooting

@user_614098468218339348, https://eveseat.github.io/docs/troubleshooting/

any log in particular that would be helpful, I didn't see anything myself when glancing

Laravel logs

If there is an error, there will be an entry in your laravel logs

The second one is just generated by checking my own skill sheet.

Is your seat-web version greater than 5.0.29? 5.0.29 should contain a fix so it at least doesn't crash. The root cause of your error is an outdated SDE that doesn't contain the name of a skill you trained. However, you can't currently upgrade your SDE because we have to change the way we import the SDE (and the new way isn't ready yet).

I believe I am on 5.0.29, but a screenshot of current versions will follow. I was just looking at the process for updating all the packages. Is this the new skills added for the mining destroyers and command destroyers not registering yet properly?

you are on 5.0.28 according to that image. seat-web at the bottom

ahhhh, I see.

I will perform updates, I think I have the correct process on the website, and if I have further problems I will let you know. Thank you for your time, kind sir.

it not loading charter info

o/ I'm having an issue with SeAT unable to start since this morning. Here is the relevant part of the logs :

[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)    Updating dependencies
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)    Your requirements could not be resolved to an installable set of packages.
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)    
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)      Problem 1
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)        - eveseat/eveapi is locked to version 5.0.31 and an update of this package was not requested.
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)        - eveseat/eseye 3.2.0 requires web-token/jwt-signature-algorithm-rsa ^3.0 -> satisfiable by web-token/jwt-signature-algorithm-rsa[3.4.8].
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)        - eveseat/eveapi 5.0.31 requires eveseat/eseye ^3.2 -> satisfiable by eveseat/eseye[3.2.0].
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)        - web-token/jwt-library 3.4.8 requires paragonie/sodium_compat ^1.20|^2.0 -> found paragonie/sodium_compat[dev-master, v1.20.0, ..., v1.x-dev, v2.0.1, ..., v2.5.0] but these were not loaded, because they are affected by security advisories. To ignore the advisories, add ("PKSA-8x19-j2j3-bn67") to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
[2025-12-31  11:22:23]    (eve-seat-5b4d86995d-ddwcm eve-seat-scheduler)        - web-token/jwt-signature-algorithm-rsa 3.4.8 requires web-token/jwt-library ^3.3 -> satisfiable by web-token/jwt-library[3.4.8].

Looks like it's this specific line :

- web-token/jwt-library 3.4.8 requires paragonie/sodium_compat ^1.20|^2.0 -> found paragonie/sodium_compat[dev-master, v1.20.0, ..., v1.x-dev, v2.0.1, ..., v2.5.0] but these were not loaded, because they are affected by security advisories. To ignore the advisories, add ("PKSA-8x19-j2j3-bn67") to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.

https://news.ycombinator.com/item?id=46435614

Hmm. Why doesn't composer select paragonie/sodium_compat v2.5.0? That should not be affected and I don't see why it can't use that

hm

composer update snafu?

Rebuilding the containers seems to fix it. However, in that case, we run into another issue:

    - laravel/framework is locked to version v10.50.0 and an update of this package was not requested.
    - laravel/framework v10.50.0 requires tijsverkoyen/css-to-inline-styles ^2.2.5 -> satisfiable by tijsverkoyen/css-to-inline-styles[v2.4.0].
    - symfony/css-selector v8.0.0 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement.
    - tijsverkoyen/css-to-inline-styles v2.4.0 requires symfony/css-selector ^5.4 || ^6.0 || ^7.0 || ^8.0 -> satisfiable by symfony/css-selector[v8.0.0].

It looks like tijsverkoyen/css-to-inline-styles added support for symfony/css-selector, but symfony/css-selector needs php 8.4

so we're in dependency hell atm? 😄

https://tenor.com/view/thegoon-bigoldgoon-ted-lasso-yes-yes-yes-yes-gif-701975896996955852

https://tenor.com/view/too-much-fun-letterkenny-wayne-gif-24904552

Having a look now

Ive been testing locally and just bumping to php 8.4 should solve the issues and sees to be fine in all the testing I have done (not 100% coverage but better than nought)