[05:03:15]
<starlord> Howdy folks, looking for some quick help. I installed Synapse to https://sub.domain.tld and everything went well, but the "Server info for clients. (well-known)" ended up at https://domain.tld/.well-known/matrix and it's preventing me from putting other apps on the main domain. Any way I can tweak this?
[10:36:46]
<Salamandar> @josue:tille.ch that's for you
[13:56:31]
<Josué> > <@starlord117:matrix.org> Howdy folks, looking for some quick help. I installed Synapse to https://sub.domain.tld and everything went well, but the "Server info for clients. (well-known)" ended up at https://domain.tld/.well-known/matrix and it's preventing me from putting other apps on the main domain. Any way I can tweak this?
Hello, now for some reason synapse need to be installed on the whole domain. But note that the yunohost domain on which you will install synapse could be different than the server name used for the user id.
[13:57:22]
<starlord> Are you saying I should uninstall it and reinstall it somewhere else but use the main domain as the address?
[13:57:51]
<Josué> Yes exactly.
[13:58:31]
<starlord> Alright, I'll give it a shot.
[14:00:40]
<Josué> By example on my side it's installed on matrix.domain.tld but my username is @josue:domain.tld
[14:01:45]
<starlord> Yes, I have it installed on mx.domain.tld and my address is @starlord:domain.tld but, despite being installed at mx.domain.tld it put domain.tld/.well-known/matrix under the main domain instead of under the mx sub.
[14:02:45]
<Josué> Yes this is normal. This is needed to make the federation working well.
[14:03:46]
<starlord> So, even if I install Synapse under the subdomain, it will create the .well-known file under the main domain, rendering me unable to use the main domain for anything else?
[14:04:14]
<3dart> Ohh man, I think its not entire computer recovery. like veeam for linux. Also its complex imo.
Btw, anyone tried veeam linux recovery for the vps?
[14:06:04]
<Josué> No normally you can use the main domain for other thing. If it's not the case it's a bug.
[14:06:14]
<starlord> Ok, perhaps I configured it improperly when installing. I will remove and reinstall and see if I can make it do something else.
[14:09:02]
<Josué> Note that you can also use the change URL to change the synapse domain.
[14:12:14]
<starlord> https://aria.im/_matrix/media/v1/download/matrix.org/lvdebsljHkbKnLFpLAWeTtzn
[14:12:16]
<starlord> The url is currently assigned to https://mx.domain.tld so there's no need to change it, but the .well-known/matrix ended up under the main domain despite installing to the subdomain mx and I can't change that.
[14:13:03]
<starlord> So the URL is already at the subdomain, it's just that the main domain has the .well-known occupying it instead of .well-known *also* being under the subdomain
[14:13:52]
<starlord> But there's no button to move the "Server info for clients" just a button to move the access url, which is already at the correct subdomain
[14:18:55]
<Josué> Yes because the server name can't be changed after the install. If you want to change it you must reinstall.
[14:19:29]
<starlord> Ok, will give that a try.
[14:19:59]
<Josué> But normally having a path on well-known shouldn't be a problems. What is your problems about that ?
[14:21:24]
<starlord> https://aria.im/_matrix/media/v1/download/matrix.org/KaBdXndZkenKEEsxSOpbZdwQ
[14:21:24]
<starlord> Trying to put another app as the main domain at the root
[14:26:22]
<Josué> OK so this is definitively a bug. And if I remembered it's maybe a known bug on the core.
[14:26:56]
<starlord> so reinstalling might not change it?
[14:27:23]
<Josué> A workaround would be maybe to install the other app before and then install synapse. This way it might work
[14:27:48]
<starlord> ok, I can try that
[14:30:01]
<Josué> > <@josue:tille.ch> OK so this is definitively a bug. And if I remembered it's maybe a known bug on the core.
Probably this one https://github.com/YunoHost/issues/issues/684
[23:18:31]
<xananax> I have two separate problems on two separate servers (both with nextcloud). The first one tells me:
> OCP\\HintException: \[0\]: Memcache \\OC\\Memcache\\APCu not available for local cache (Is the matching PHP module installed and enabled?)
See log: https://paste.yunohost.org/raw/oxayowipom
For the second, it's 100% my fault. I'm on my day off so I upgraded all my servers, and I mistakenly pressed ctrl+c in this one, during the nextcloud install.
See log: https://paste.yunohost.org/raw/pucivacufu
[23:33:33]
<xananax> I have two separate problems on two separate servers (both with nextcloud). The first one tells me:
> OCP\\HintException: \[0\]: Memcache \\OC\\Memcache\\APCu not available for local cache (Is the matching PHP module installed and enabled?)
See log: https://paste.yunohost.org/raw/oxayowipom
For the second, it's 100% my fault. I'm on my day off so I upgraded all my servers, and I mistakenly pressed ctrl+c in this one, during the nextcloud install.
It now says:
> Command '['git', 'ls-remote', '--symref', 'https://github.com/YunoHost-Apps/nextcloud_ynh', 'HEAD']' returned non-zero exit status 128.
See log: https://paste.yunohost.org/raw/pucivacufu
[23:49:12]
<xananax> I have two separate problems on two separate servers (both with nextcloud). The first one tells me:
> OCP\\HintException: \[0\]: Memcache \\OC\\Memcache\\APCu not available for local cache (Is the matching PHP module installed and enabled?)
See log: https://paste.yunohost.org/raw/oxayowipom
For the second, it's 100% my fault. I'm on my day off so I upgraded all my servers, and I mistakenly pressed ctrl+c in this one, during the nextcloud install.
My nextcloud directory is empty as a result
It now says:
> Command '\['git', 'ls-remote', '--symref', 'https://github.com/YunoHost-Apps/nextcloud\_ynh', 'HEAD'\]' returned non-zero exit status 128.
But I'm not sure it's related, I feel it might be a coincidence
See log: https://paste.yunohost.org/raw/pucivacufu