thany

Can you explain how to do this? I know what a SRV record is, and I know how to add one. But what should it contain exactly? Should I put "_matrix._tcp.matrix.example.com" in there, given "example.com" is my domain? Or do I put in "_matrix._tcp.example.com"? And what are those "_matrix" and "_tcp" parts? And where do I put port 443? What does DNS have to do with port numbers?

When I try that, I get this: $ register_new_matrix_user -c /data/homeserver.yaml http://0.0.0.0:8008 New user localpart [matrix]: Password: Confirm password: Make admin [no]: yes Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/urllib3/connection.py", line 170, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/local/lib/python3.7/dist-packages/urllib3/util/connection.py", line 96, in create_connection raise err File "/usr/local/lib/python3.7/dist-packages/urllib3/util/connection.py", line 86, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 706, in urlopen chunked=chunked, File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 394, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/local/lib/python3.7/dist-packages/urllib3/connection.py", line 234, in request super(HTTPConnection, self).request(method, url, body=body, headers=headers) File "/usr/lib/python3.7/http/client.py", line 1244, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1290, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1239, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1026, in _send_output self.send(msg) File "/usr/lib/python3.7/http/client.py", line 966, in send self.connect() File "/usr/local/lib/python3.7/dist-packages/urllib3/connection.py", line 200, in connect conn = self._new_conn() File "/usr/local/lib/python3.7/dist-packages/urllib3/connection.py", line 182, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x1544ebed7198>: Failed to establish a new connection: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/dist-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py", line 756, in urlopen method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] File "/usr/local/lib/python3.7/dist-packages/urllib3/util/retry.py", line 573, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='0.0.0.0', port=8008): Max retries exceeded with url: /_matrix/client/r0/admin/register (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x1544ebed7198>: Failed to establish a new connection: [Errno 111] Connection refused')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/register_new_matrix_user", line 20, in <module> main() File "/usr/local/lib/python3.7/dist-packages/synapse/_scripts/register_new_matrix_user.py", line 221, in main args.user, args.password, args.server_url, secret, admin, args.user_type File "/usr/local/lib/python3.7/dist-packages/synapse/_scripts/register_new_matrix_user.py", line 134, in register_new_user user, password, server_location, shared_secret, bool(admin), user_type File "/usr/local/lib/python3.7/dist-packages/synapse/_scripts/register_new_matrix_user.py", line 43, in request_registration r = requests.get(url, verify=False) File "/usr/local/lib/python3.7/dist-packages/requests/api.py", line 76, in get return request('get', url, params=params, **kwargs) File "/usr/local/lib/python3.7/dist-packages/requests/api.py", line 61, in request return session.request(method=method, url=url, **kwargs) File "/usr/local/lib/python3.7/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/local/lib/python3.7/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/local/lib/python3.7/dist-packages/requests/adapters.py", line 516, in send raise ConnectionError(e, request=request) requests.exceptions.ConnectionError: HTTPConnectionPool(host='0.0.0.0', port=8008): Max retries exceeded with url: /_matrix/client/r0/admin/register (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x1544ebed7198>: Failed to establish a new connection: [Errno 111] Connection refused')) So that's not good, is it? How do I make it not refuse the connection?

This. Synology could find usecases for this, because the usecases are there. What they are, is open to speculation, and not awefully relevant to the question whether we should have this feature in a future version, or not. Also keep in mind that if you specifically DON'T want a file manager built graphically into the WebUI, power to you - you're free to ignore it, and it won't get in your way. Everyone is different, and since unRAID is being used in a variety of scenarios, you can't say something always makes sense, or indeed never makes sense. I think this topic has proven that many people would like this built into the WebUI (and it could even be offered as an official plugin) so it makes sense to, at the very least, get this onto some sort of todo list for the authors, if not already.

It errors for me as well, telling me links aren't supported. Can you please make a version where MongoDB is integrated into the package? This would certainly avert a lot of problems (see above) and would make it easier to get started. The way I understand Docker, is that a docker should be self-contained. So it should contain everything it needs to run, and only go to the "outside world" for file system storage, and configuration files. If you are unable to do this, could you at least make an easy to follow "getting started" guide? Docker being Docker, and unRAID being unRAID, it should be more or less identical for nearly everyone.

Default settings should always at least do *something*. If default settings give all kinds of errors, or plainly don't work at all, they are wrong. All unRAID installations concerning the docker daemon, are virtually identical. This docker is in the CA repo, so it ought to work. If special instructions are vitally important, they should be more visible right then & there, before/while/after installing. This is not something you should do, of course, assuming you didn't build the CA plugin. Not sure where to report that, so I hope a CA developer is reading along.

But whatever the docker comes with, should at least work. Settings can be adjusted later, but for a bog standard install, it should just work.

OnlyOffice is super slow to install itself. The docker image installed just fine, but when first opening the web UI, of course onlyoffice needs to set itself up. This is taking forever! It's currently using about one of my four cores (on average) and I'm not sure where I can see I/O usage. But it's definitely doing something. How long does it normally take? Given that it's singlethreaded, it shouldn't make very much difference from system to system how long it needs for this process. I mean, is it minutes, 10's of minutes, hours? Just a ballpark estimate would be nice to know.

Just installed UNMS, but when I open the web UI, my browser says "Secure Connection Failed" with code SEC_ERROR_INADEQUATE_KEY_USAGE.

Are those neccesary settings not the default settings then? If not, they should be, right?

It's not working. Just did a plain vanilla default installation. So no need to post my config - it's absolutely bog standard. Opened the web UI and... "Unable to connect" It just doesn't work.

That's the thing. It won't happen again just by doing the same thing. Can you think of *any* reason whatsoever why it might crash the server? Maybe I can diagnose it from that angle.

Ah, I think you're right Well if nothing else, it's quite hard for me to confirm I've got the latest version. In the client, I'm seeing 2.92 (14714), but I can't find that version number anywhere on the docker hub or the github page, or in this thread. So I feel uncertain whether I'm *actually* up-to-date... /edit When I say "the client", I mean Transmission Remote GUI 5.0.1.

I just clicked the Apps tab and my server crashed. It just looked like it was taking a long time, and after a few minutes I just hit F5 and it instantly worked, with a server uptime of 1 minute. It can't be a coincidence - I literally only clicked the Apps tab. Nothing more. And then, crash. Reboot. I'm not sure where to go for logs on what actually happened. Any ideas? As for my server: I'm at 6.4.0. I think everything is up to date.

I got a notification from unraid there's an update to transmission, but when I go into the Docker tab and hit "check for updates", it says transmission is already up-to-date. I think it hasn't updated for a good number of weeks now, and usually there's an update every week or two... Any ideas?

I can imagine a very small amount, like 1GB, should suffice when unraid is used purely as a fileserver. I personally have got 16GB installed, because I'm running a few VMs and a couple of dockers. I also like the idea of filecache in memory, and a bit of overhead in case when something really needs it, has never hurt anyone. Also, memory is quite cheap, so why not.

I don't use them. My unraid box only has SSD's anyway. Spinning up/down is purely a legacy function from my perspective. On spinning harddisks, this is something that can be automated perfectly. Power management should be able to handle spinning disks up/down when it makes sense. There's absolutely no need for anyone to configure this manually, unless in case of a control freak. Better not clutter unraid with unneccesary functions, iyam.