This could be correct, but we would still consider this a TrueNAS bug since we expect to support those VMs. Can you report as a bug and share your debug info etc.
I raised bug report.
After 24 hrs I attempted agin to upgrade to 25.04.1 and this time ther was no VM but same issue occured . so the issue related to update rather than to VM.
Could you share the NAS-Ticket number?
Two benefits of not sharing IP addresses include
- password managers not getting confused whether you want to log into dockge, portainer, pi-hole, or the admin UI, among other things - though this is clearly a limitation on the part of the password manager.
- allowing a simpler implementation of shared services such as pi-hole DNS, plex server on a VLAN for the network, etc.
Not to say that these are good reasons, and in an ideal world, it would be great to start a resource around this issue since it seems to confuse so many folk.
2 Likes
Bitwarden, at least, lets you set the matching pattern. It defaults to matching on the domain, but can be set to match on the FQDN, or the exact address (including port), or whatever. I can’t speak for others though.
1 Like
Theoretically, so does 1Password 7, but for whatever reason the port number omission or presence is usually ignored. I may be switching to strongbox pro and there is hope that will be more advanced.
That’s why I create aliases in my local DNS for each service. Unbound in OPNsense supports that quite nicely.
Also helps with browsers insisting on using SSL if that was successful once in the past, regardless of the different port number.
I would love to update, but when I press “Check for Updates” on the Dashboard, I get this error?!
“Cannot connect to host update.ixsystems.com:443 ssl:default [Temporary failure in name resolution]”
More info gives me this:
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 1317, in _create_direct_connection
hosts = await self._resolve_host(host, port, traces=traces)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 971, in _resolve_host
return await asyncio.shield(resolved_host_task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 1002, in _resolve_host_with_throttle
addrs = await self._resolver.resolve(host, port, family=self._family)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/resolver.py”, line 38, in resolve
infos = await self._loop.getaddrinfo(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/asyncio/base_events.py”, line 868, in getaddrinfo
return await self.run_in_executor(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/socket.py”, line 962, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -3] Temporary failure in name resolution
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/api/base/server/ws_handler/rpc.py”, line 323, in process_method_call
result = await method.call(app, params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/api/base/server/method.py”, line 40, in call
result = await self.middleware.call_with_audit(self.name, self.serviceobj, methodobj, params, app)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 883, in call_with_audit
result = await self._call(method, serviceobj, methodobj, params, app=app,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 703, in _call
return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 596, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 178, in nf
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/update.py”, line 105, in get_trains
trains_data = self.middleware.call_sync(‘update.get_trains_data’)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1002, in call_sync
return self.run_coroutine(methodobj(*prepared_call.args))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 1042, in run_coroutine
return fut.result()
^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/_base.py”, line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/_base.py”, line 401, in _get_result
raise self.exception
File "/usr/lib/python3/dist-packages/middlewared/plugins/update/trains.py", line 63, in get_trains_data
**(await self.fetch(f"{self.update_srv}/trains.json"))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/update/trains.py", line 25, in fetch
async with client.get(url) as resp:
File “/usr/lib/python3/dist-packages/aiohttp/client.py”, line 1359, in aenter
self._resp: _RetType = await self._coro
^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/client.py”, line 663, in _request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 563, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 1032, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/aiohttp/connector.py”, line 1323, in _create_direct_connection
raise ClientConnectorDNSError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host update.ixsystems.com:443 ssl:default [Temporary failure in name resolution]
Your DNS server is probably misconfigured.
Check Network > Global Configuration
2 Likes
If the suggestion from @pmh doesn’t pan out, I suggest you post your own thread as it’s easier to assist you in a dedicated thread, instead of hijacking the release thread.
1 Like
That was indeed the issue, I must have lost the nameservers when I toyed with a few extra network adapters.
Thanks a lot!
2 Likes
It can be especially if you rush to update to a .0 or .1 release. I wait until at LEAST .2, and even then, depends on what I am reading. For Fangtooth, probably not even .4 as Incus is too much trouble currently as is.
This is the NAS Ticket No: NAS-136336
I’m pleasantly surprised that it is as nice to use as it is. However migration of my files has been painfully slow due to SMB speed held at 11 MB/sec. Compared to Core which is 10X faster. It’s been a lengthy process. Can we assume it’s just a setting in php that needs to be tweaked?
Being locked at 11 MB/sec sounds like fast ethernet. Maybe check your cabling. A shoddy gigabit cable can downgrade to 100mb/s.
Actually I have Gigabit throughout my place. Use Cisco Switches and get fabulous throughput. This dog don’t hunt. Many people complaining about TrueNAS Scale 25.04.1
Are you saying you verified your network health and speed with a tool such as iPerf?
You gave very little information on what steps you have taken or how you are coming to your conclusion of slow SMB speeds. Provide as much details as you can. If it is related to some SMB settings, I have found @awalkerix to be knowledgeable and helpful on the forums.
iX Systems has to be able to reproduce the problems on their end. I think most of the slow SMB has been network issues and non standard SMB settings.