Oui, mais à quoi est-ce que tu penses par exemple ?
N.B. : en étant admin, tu peux facilement passer root avec 'sudo su'
Oui, mais à quoi est-ce que tu penses par exemple ?
N.B. : en étant admin, tu peux facilement passer root avec 'sudo su'
Je pensais aux logs des mails, par exemple, ou php.
Minor version 3.4.2.3 was released and should fix the following :
I was on yunohost “beta” to try 3.4, now that it is out, how can I switch back to stable?
You should already be in 3.4.2.x (the stable release) but if you want to avoid upgrading to the next testing, you can edit the repo config using nano /etc/apt/sources.list.d/yunohost.list
then replace ‘testing’ by ‘stable’, save, and do an apt update
(it never hurts)
Hello, the upgrade worked well, globally, except for one package : onlyoffice (not stable at this time I know).
I think there is a problem with nginx conf files and headers. But I don’t if the pb is linked to Yunohost or specific to the package.
Here the error I have :
La ressource à l’adresse « https://cloud.monsite.com/yunohost/sso/?r=aHR0cHM6Ly9jbG91ZC5oYW5uZWJlcnQuY29tL3luaHBhbmVsLmpz » a été bloquée en raison d’un type MIME (« text/html ») incorrect (X-Content-Type-Options: nosniff).
I reported it on github : https://github.com/YunoHost-Apps/onlyoffice_ynh/issues/6#issuecomment-462032427
I would appreciate any help
Hmmokay, I’m not sure but it could be related to a change in the nginx header (add_header
-> more_set_headers
) but one would need to investigate deeper to really understand what’s going on :s
I could try in deleting the added header in nginx conf files for nextcloud domain and/or onlyoffice domain. Is it dangerous ?
Thanks!
Soooo pre-installed images for ARM boards were upated !
They should be working well and everything (been checking RPi and orangepi PC+), but it wouldnt hurt if some people could validate them on their side as well.
In particular, I’m interested if someone could test the RPi image on an HDMI screen to see if the whole initial bootprompt thing really does work nicely now. (It has only been tested in a virtualbox)
J’ai ce problème pour l’accès SFTP a mes webapp également…
Salut !
Je n’ai lancé la migration SSH que aujourd’hui, petit retour d’expérience
Etat des lieux avant la migration
my_ssh_port
différent du port 22 (qui était bloqué), j’avais suivi le tuto YunoHost • indexmy_ssh_user
qui n’était ni admin
ni root
.PasswordAuthentication no
dans /etc/ssh/sshd_config
).ssh -i ~/.ssh/id_rsa -o IdentitiesOnly=yes -p my_ssh_port my_ssh_user@IP
→ Lancement de la migration
Après la migration
yunohost-api
était démarré donc ouverture du port via l’interface admin webmy_ssh_user
vers admin
22
à my_ssh_port
, et bloquer le port 22PasswordAuthentication no
dans /etc/ssh/sshd_config
Pour finir petit conseil utile : pensez à ouvrir le port 22 avant de lancer la migration et démarrer le service yunohost-api
pour conserver un accès admin au cas où …