Installation Mastodon OK... Mais le compte ne marche pas : 401The access token is invalid

Bonjour,

J’ai bien installé Mastodon et paramétré un profil.
(J’ai déjà une expérience d’utilisateur sur Mastodon)

Mais je n’arrive pas à utiliser, le compte (peux pas envoyer de pouet, pas télécharger une image…)

J’ai des

401The access token is invalid

Merci de vos retours.

Amicalement, José

Hi,
Thank for making Mastodon available on YNH.

I have installed and updated Mastodon to the 2.9.2~ynh1.

But always the “401The access token is invalid” error message.

Not, I had an issue of admin page access. It’s ok now.

Thank you for any feedback or trail.

Have a nice and hot week :slight_smile:
José

Hi @yalh76,

About this issue with Mastodon,
I noted this 2017 issue: 401: Access token invalid · Issue #4223 · mastodon/mastodon · GitHub

Conclusion was:

I’m now closing this issue as this appears to be related to the time on the server being out of sync. Since getting the correct time set on the server these errors have seemingly stopped (at least for now). Unfortunately none of the debugging output really pointed me towards this being a time related issue so it took a fair amount of experimenting with different things to resolve. Apologies for seemingly wasting peoples time over something quite trivial.

The key point seems to be to the time on the server being out of sync.

Thank you if you can analyze it and share a solution for non-coders.

Have a good time, José

First point, check the time of you YunoHost doing date and compare to the time on your computer.

Hi @yalh76
Thank you for the feedback.

Exemple:
Wed Aug 14 11:22:41 CEST 2019

This is ok :slight_smile:

Did you install your instance as a private instance?

Hi,
I will say no,
It is open to all public.

Bonsoir,
J’ai la même erreur. Je peux me connecter avec mon compte, mais rien n’apparait dans le fil public. Lorsque je rajoute des comptes à suivre c’est la même chose, je ne les vois pas non plus.
Et régulièrement j’ai le même message d’erreur qui apparait sur mon écran.

Good evening,

I have the same mistake. I can login with my account, but nothing appears in the public thread. When I add accounts to follow it’s the same thing, I do not see them either.
And regularly I have the same error message that appears on my screen.

1 Like

I have the same problem, and my date is OK.
The quick and dirty workaround here here works, but I’d prefer a slow and clean one.

HI,

I noted in the Brique camp 2017, the following output:

# Correction de bogues

Erreur de token sur mastodon, peertube et bitwarden

Could you share your answer?

Thank you, José

Hi @mackemint
Thank you for sharing this issue closed in 2017

magikcypress closed this on 30 Apr 2017

Thank you if you can share, for non-coders, what you did :slight_smile:

Last comment from @aslmx

commenting out the line mentioned at the beginning of the thread, restarting nginx and the 3 mstdn services seems to have fixed it .

Thank ou in advance, José

Bon bah… ça marche !!! Et j’ai rien fait.

j’ai juste fait des reboots en mode rescue et normaux sur mon VPS, mon mot de passe root ne répond plus !

Je peux communiquer avec mon Mastodon de Framapiaf, même le bot de la FEDERATION m’a tracé !!! :sunny: :smile: :wink: :stuck_out_tongue_closed_eyes: :upside_down_face:

J’attends quand même quelque jours avant de le fermer :star_struck:

Amicalement, José

Lors d’une installation fraiche j’ai le message d’erreur suivant (dans le défilement de progression.

perl: warning: Falling back to the standard locale (“C”).
are supported and installed on your system.
LANG = “fr_FR.UTF-8”
LC_ALL = (unset),
LANGUAGE = (unset),
perl: warning: Please check that your locale settings:
perl: warning: Setting locale failed.

warning " > react-redux-loading-bar@4.0.8" has incorrect peer dependency “react-redux@^3.0.0 || ^4.0.0 || ^5.0.0”.

/opt/rbenv/versions/2.6.1/lib/ruby/site_ruby/2.6.0/rubygems/ext/builder.rb:191: warning: conflicting chdir during another chdir block

/opt/rbenv/versions/2.6.1/lib/ruby/site_ruby/2.6.0/rubygems/ext/builder.rb:183: warning: conflicting chdir during another chdir block

/opt/rbenv/versions/2.6.1/lib/ruby/site_ruby/2.6.0/rubygems/ext/builder.rb:191: warning: conflicting chdir during another chdir block

/opt/rbenv/versions/2.6.1/lib/ruby/site_ruby/2.6.0/rubygems/ext/builder.rb:183: warning: conflicting chdir during another chdir block
Installing Mastodon…
tr: write error: Broken pipe

Est-ce que cela peux avoir une incidence sur l’erreur de jeton ?

A priori nous avons identifié le probléme avec @Aleks : Add setting for apps to disable Basic HTTP Auth header injection in some uris · Issue #1420 · YunoHost/issues · GitHub

2 Likes

@yalh76
Hi, thank you for this feedback.
My understanding is, today, you do not have a solution.
(And the 2017’s solution is no more relevant.)

Thank you for your time.

Please note I have reinstalled YUNOHOST and Maston and I’ve got the same behavior: installation is very easy but this 401 error messsage poped up :slight_smile:

May I suggest to mention this in the Readme file of mastodon_ynh.

Thank you again and
Have a good weekend, José

@yalh76, @Guillermo, @Aleks, @ljf

Génial, cela marche bien… en navigation incognito (FF) !
Le compte d’admin (temporaire): @bas@m.bacasable.eu
et le compte user :sunny: @jose@m.bacasable.eu

@yalh76, je t’ai envoyé un pouet :slight_smile:

Fantastic, it works in incognito navigation (FF)!
Temporary instance. @jose@m.bacasable.eu

If you want an account for testing: https://m.bacasable.eu/about

Thank you again
Have a nice evening, José

Qu’as tu fais pour que cela fonctionne ?

Merci

En fait j’ai tout réinstallé : serveur + Mastodon 2.9.3~ynh1 (cette version est toute récente).

Sur Firefox, en navigation normale, cela ne fonctionne pas (401)

Mais si tu utilises le navigateur en mode Privé (Ctrl + Maj +P), Mastodon fonction normalement :slight_smile:

Merci du retour. José

Ce serait tentant, mais j’ai trop de choses dessus, serveur email etc.
Pourtant je suis exactement dans les mêmes versions de firmware de mastodon ou yunohost, je vais attendre un peu encore de voir si les choses évoluent.

@Guillermo

Tu as essayé d’ouvrir ton Mastodon avec un navigateur en mode privé ?