[05:12:24]
<Fritjof> How can I reset the login attempts on funkwhale via yunohost? I tried to log on the app (forgot httpsv//) and now keep getting: login failed too many requests.
[05:13:52]
<Fritjof> How can I reset the login attempts on funkwhale via yunohost? I tried to log on the app (forgot httpsv//) and now keep getting: login failed too many requests.
[06:30:07]
<Fritjof> Is it really enough for remote/web access to an old home PC with YNH to setup a ddns domain like *.noho.st in the server, and activate upnp on bothe the router and server, to be up and running?
Don't I need to put the info from my YNH dynDNS somewhere in the router?
[06:31:30]
<Fritjof> It seems to have been working fine for the past few days, but I wonder if it really is because it is working or because my IP hasn't changed.
I worry that if it changes all will fail.
[06:39:56]
<ChriChri> > <@fritjof:deepfunk.dk> Is it really enough for remote/web access to an old home PC with YNH to setup a ddns domain like *.noho.st in the server, and activate upnp on bothe the router and server, to be up and running?
> Don't I need to put the info from my YNH dynDNS somewhere in the router?
As far as I know the default setup is that yunohost runs the dyndns task (ddclient).
I disabled for various reasons ddclient on my ynh and am using the dyndns function of my router (it knows when the IP changes, because it drives the pppoe and I can react to that event).
The dyndns protocol is just a https connection to a server telling it to update your dns record. There are hosts on the net anybody can ask "hey, what is my IP number you see on your side". This combined leaves it open to any host behind a nat firewall to update any dns record by asking for its IP and then sending that IP to the dyndns server.
[06:44:35]
<Fritjof> Great, so I can just leave it as is?
[07:12:16]
<Fritjof> awesome!
[07:13:56]
<Fritjof> I still get an error in the health of YNH saying reverse DNS is not configured properly. Is it possible to configure this (on a tp-link router) and still use UPnP and YNH dynDNS ?
[07:16:41]
<ChriChri> > <@fritjof:deepfunk.dk> I still get an error in the health of YNH saying reverse DNS is not configured properly. Is it possible to configure this (on a tp-link router) and still use UPnP and YNH dynDNS ?
You can keep the setting on the ynh. The reverse DNS you cannot change. That would need to be done by the owner of the IP-address - your provider. They won't. The reverse DNS record is mostly important for email: you'll not likely be able to send email to many systems, because your claimend domain does not fit the information the receiving end would find if they'd look for a FQDN for your IP...
[07:17:36]
<Fritjof> OK.
[07:21:53]
<Fritjof> last question: OpenVPN - can I usee that with my router while using YNH dynDNS?
[07:27:32]
<ChriChri> If you do not use ports for OpenVPN that ynh would like to open. The obvious example is if you ran your OpenVPN on tcp:443. Your router would either accept connections to its official IP for your OpenVPN **or** forward them to your ynh. So make sure whatever ynh wants to open for incoming connections is not used by a service on your router.
If you want to avoid confusion and really take control you could disable upnp and follow the ynh instructions on which ports need to be forwarded. You could configure that manually. But there is no real need to do so.
[07:28:14]
<Fritjof> Many thanks for these answers
[07:30:18]
<ChriChri> > <@fritjof:deepfunk.dk> Many thanks for these answers
Your welcome! If you find time and motivation you could look at the documentation if we could fit the missing information in somewhere without bloating it or if it could go in some kind of FAQ (I'm still new to ynh myself and do not know all of the places to look ;-) ). Contributing is very welcome, just using and telling others, also!
[07:31:32]
<Fritjof> Thank you. I will definetly try that :)
[10:55:20]
<Fritjof> I have a problem with upnp disabling on my server after a reboot
[11:06:30]
<ChriChri> > <@fritjof:deepfunk.dk> I have a problem with upnp disabling on my server after a reboot
Uhm, sorry, cannot help on that - I have a general problem with upnp and like to have control. I disabled it first thing when I started with ynh and configured everything static.
[11:07:25]
<Fritjof> Probably what I'll do eventually also.
[15:31:51]
<bamf> > <@bamf:matrix.f1sh.de> has anyone tried yet if the Synapse `1.94.0~ynh1` update is working? after last update it was completely broken and even could not be recovered from a backup
anyone? :)
[15:52:52]
<Chatpitaine Caverne> bamf: What symptoms ? I had to authorize user login cause CAS didn't work anymore, but that's all.
[15:54:38]
<Chatpitaine Caverne> Your restauration issue could be link to this : https://forum.yunohost.org/t/synapse-update-fails-impossible-to-restore/26735
[15:54:46]
<bamf> > <@chatpitaine:cirkau.art> bamf: What symptoms ? I had to authorize user login cause CAS didn't work anymore, but that's all.
there was a dependency issue with setuptools
[15:54:49]
<bamf> yes exactly
[15:55:12]
<Chatpitaine Caverne> > <@bamf:matrix.f1sh.de> there was a dependency issue with setuptools
So that's it. The issue with common-sh shell.
[15:56:04]
<bamf> so it's safe to upgrade to `1.94.0~ynh1` now?
[15:58:03]
<Chatpitaine Caverne> I ran this update and had no issue. But if you have to restore, then the issue with setuptools gonna trouble restauration and you'll have to modiffy common.sh in the tar file.
After this upgrade the culprit shell has been corrected.
[15:59:24]
<bamf> yes I already ran through this hell with common.sh :D thanks, I'll try the upgrade then
[16:18:59]
<Salamandar> yunohost.org