Hardware: VPS bought online YunoHost version: 11.1.17 I have access to my server : Through SSH | through the webadmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no If your request is related to an app, specify its name and version: My_WebApp 1.0~ynh13
Do I have to change config of SSH or could be something wrong with it? I looked at a lot of documentation about password authentication and public SSH keys but a bit afraid of touching any of it. Like this My_webapp | Yunohost Documentation
Is there a user “my-webapp” somewhere because there isnt a directory in /home or /home/yunohost.app and also not in Yunohost web admin.
What am I missing?
Aside:
I’m looking for a place to upload OPML files to have another app (FreshRSS) to dynamic populate its feeds based on OPML files I maintain seperatly. FreshRSS needs these OPML files to be in a public place. So I created a specific subdomain and installed a “My WebApp” to make this possible, which started this rabbithole (kind of). Suspecting I need other instances of “My WebApp” in the future, so better I fix this from the get-go.
Changed the my_webapp password, with “sudo -s passwd my_webapp” and changed it to the same as given during install of My_WebApp.
Now SSH stays blank and SFTP just says: “Cant connect to server”.
Forgot to mention after install I changed the password also in the application config screen in de webadmin, when inlog with SFTP didnt work. Dont know if it should have been the same effect as this command?
Not sure if it provides more info but I SSH with my admin account and did this:
root@xxxxx:/# sudo su my_webapp
Gave this: “This account is currently not available.”
The user my_webapp have only access to SFTP (not SSH)…
Juste discovered this. But nothing to do with your problem I think.
One thing worked for me, is to uninstall my_webapp completely, and then make a fresh install with the same domain… After that it was possible to SFTP for my_webapp new user.
It was possible because my Webapp has only static HTML, no database, no dynamic content… In clear, nothing to backup.
You can also create for testing purpose a new fresh Webapp, and see if this user (if it’s the second one it’s my_webapp__2) can connect with SFTP.
Same result, wiped the ‘old’ one, installed fresh.
SFTP with admin-user works like a charm, SFTP with my_webapp …
“Cant connect to server” with FileZilla and WinSCP throws an error about “To big packet SFTP received” and “Cant initialise SFTP protocol” and the question if there is an SFTP service at the target machine.
[WARNING] DNS resolution seems to be working, but it looks like you’re using a custom /etc/resolv.conf.
The file /etc/resolv.conf should be a symlink to /etc/resolvconf/run/resolv.conf itself pointing to 127.0.0.1 (dnsmasq). If you want to manually configure DNS resolvers, please edit /etc/resolv.dnsmasq.conf.
In the System configurations (regenconf) section:
[WARNING] Configuration file /etc/ssh/sshd_config appears to have been manually modified.
This is probably OK if you know what you’re doing! YunoHost will stop updating this file automatically… But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with ‘yunohost tools regen-conf ssh --dry-run --with-diff’ and force the reset to the recommended configuration with ‘yunohost tools regen-conf ssh --force’
[ERROR] The SSH configuration appears to have been manually modified, and is insecure because it contains no ‘AllowGroups’ or ‘AllowUsers’ directive to limit access to authorized users.
I dont know what caused this but do I have to ‘regen’ recommended configuration?
The ‘dry-run’ mentions @@ -1,124 +1,110 @@ which seems an indicator ho much characters would have to be added/removed?
