Premium Extension Composer Error

clarkwinkelmann

So far, every time I've seen this error with a customer it was because of an expired token, and/or the new token not being properly configured (wrong Composer config file, basic instead of bearer, etc.).

But we can't exclude infrastructure issues with the marketplace.

Unfortunately I don't have a lot of hands-on experience, since I don't actually use any premium extension from the marketplace myself 😅 My own forums use the development version of my extensions straight from GitHub.

KBExit

clarkwinkelmann yeah I've made new tokens and applied them in to no success. I firmly believe this is an issue with the infrastructure.

endlessedits

For what it's worth in debugging, yesterday I updated everything and no problem, today I got that error.

KBExit

endlessedits I agree and can attest the same.
I'm sure a remedy will be out soon. 🙂

endlessedits

KBExit

Yes, to be clear, the extension kilowhat/flarum-ext-rich-embeds 1.4 still works great for me, it's just that the overall update command did not complete other available updates due to something with the remote repositories. (I'm no expert.)

luceos

There is an issue with the premium extension availability. It was reported to me last night by @maicol07 . So far I was able to see the problem occur, but not yet identify a cause.

My investigation will continue today, I will update everyone here as soon as I can.

luceos

Found the issue, all premium extensions are syncing now and should be available again within the next 15 minutes.

My apologies for the inconvenience.

Pupswoof117

For what it's worth, I'm still having issues.

KBExit

Pupswoof117 what are you being faced with? I haven't had the chance to try it yet.

Pupswoof117

KBExit it says this

`
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires maicol07/flarum-oidc-client, it could not be found in any version, there may be a typo in the package name.
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
It's a private package and you forgot to add a custom repository to find it
Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
allisonw@pi4:/var/www/forums.webpoweredlab.com
`

Pupswoof117

KBExit they approved it, disregard this reply.

KBExit

Pupswoof117 I see your reply.
Did you try creating a new token first and adding it to your Flarum instance first?

Pupswoof117

KBExit repeatedly

Pupswoof117

Maintainer said it worked, I haven't seen that on my end.

Pupswoof117

Maybe its not refreshed for north America?

Pupswoof117

It could be one thing, could be multiple, but I did figure out how to lock registration, under permissions in admin.

KBExit

Pupswoof117 were you running it with extension manager,? Sometimes things get hung up on it.

Pupswoof117 what does registration have to do with premium Extensions? 😅

Pupswoof117

KBExit

Question 1: with and without, should I not use it?

Question 2: it's an oidc plugin. I need to make registrations halt so people don't signup through the forum.

KBExit

Pupswoof117 if you get issues with it, it's best to try with SSH. If something gets hung up with extension manager, it stays hung until the issue clears out.
For instance, if it can't find an extension due to it being abandoned or an issue like this one, I've seen it hold in memory and continuously retry the install on it over and over again and report a failure. Even if you moved on and tried to install something else.
It's super convenient to use, especially on shared hosting, but it's limitation is with how composer behaves. Just a heads up.

mafesa

huseyinfiliz For those still running Flarum 1.x

Thanks for the update!

Flarum 1.8.13

[2026-02-25 09:43:51] composer.ERROR: require 'huseyinfiliz/stickiest:*' -W
/var/www/html/composer.json has been updated
Running composer update huseyinfiliz/stickiest --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires huseyinfiliz/stickiest *, found huseyinfiliz/stickiest[dev-master, 1.x-dev, 2.0.0-beta.1, 2.x-dev] but it does not match your minimum-stability.


Installation failed, reverting /var/www/html/composer.json and /var/www/html/composer.lock to their original content.