@olivierlambert I was not, and cert is invalid, but when I override I get the same result. I will fix the cert and try again.

@olivierlambert I'm seeing in the browser:

objc[49945]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x7ffb53eb4ec8) and /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/107.0.5304.87/Libraries/libGLESv2.dylib (0x10f0e0ed8). One of the two will be used. Which one is undefined.
[49934:259:1031/131940.589622:ERROR:account_info_fetcher.cc(62)] OnGetTokenFailure: Invalid credentials (credentials rejected by server).
[49947:11779:1031/131958.215231:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -207
[49947:11779:1031/131958.215336:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -207

And on XOA:

Oct 31 12:20:48 xoa su[95003]: (to xoa-support) root on none
Oct 31 12:20:48 xoa su[95003]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 12:20:49 xoa su[95003]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 12:40:22 xoa su[96868]: (to xoa-support) root on none
Oct 31 12:40:22 xoa su[96868]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 12:40:23 xoa su[96868]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:16:54 xoa su[115150]: (to xoa-support) root on none
Oct 31 16:16:54 xoa su[115150]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 16:16:55 xoa su[115150]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:20:17 xoa su[115514]: (to xoa-support) root on none
Oct 31 16:20:17 xoa su[115514]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 16:20:17 xoa su[115514]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:20:40 xoa xo-server[511]: 2022-10-31T20:20:40.291Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:41 xoa xo-server[511]: 2022-10-31T20:20:41.424Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:42 xoa xo-server[511]: 2022-10-31T20:20:42.387Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:43 xoa xo-server[511]: 2022-10-31T20:20:43.536Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:44 xoa xo-server[511]: 2022-10-31T20:20:44.542Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:45 xoa xo-server[511]: 2022-10-31T20:20:45.667Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:47 xoa xo-server[511]: 2022-10-31T20:20:47.771Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:48 xoa xo-server[511]: 2022-10-31T20:20:48.890Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:51 xoa xo-server[511]: 2022-10-31T20:20:51.883Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:53 xoa xo-server[511]: 2022-10-31T20:20:53.011Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:58 xoa xo-server[511]: 2022-10-31T20:20:58.117Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:59 xoa xo-server[511]: 2022-10-31T20:20:59.246Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:07 xoa xo-server[511]: 2022-10-31T20:21:07.044Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:08 xoa xo-server[511]: 2022-10-31T20:21:08.171Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:20 xoa xo-server[511]: 2022-10-31T20:21:20.646Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:22 xoa xo-server[511]: 2022-10-31T20:21:22.096Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:43 xoa xo-server[511]: 2022-10-31T20:21:43.641Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:44 xoa xo-server[511]: 2022-10-31T20:21:44.764Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)

@olivierlambert I have already restarted the tool stack.

Safari told me it can't see logs from the production build - I will try Chrome.

Where are the XO logs - that was my original question.

@olivierlambert Definitely reachable.

XO logs?

@olivierlambert 1) XOA

2. No browser log because of the stripped production build, alas; where is the XO log?

Can this possibly be a firewall issue, either on the XS server or the VMs? 80 and 443 are open but not much else.

I no longer can get consoles on my XenServer 7.0.0 (don't ask - separate topic) VMs or hosts - ideas?

@Danp no, we're a hack target...

@olivierlambert Um,... backs away shyly...

@Danp Thanks, but not the case here...

rklorese@rklorese-a01 ~ % ssh root@216.252.162.94            
root@216.252.162.94's password: 
Last failed login: Wed Apr 13 10:56:54 PDT 2022 from 61.177.173.59 on ssh:notty
There were 13 failed login attempts since the last successful login.
Last login: Wed Apr 13 10:50:47 2022 from 97-113-197-229.tukw.qwest.net
[root@marshapjohnson ~]# cat /etc/redhat-release
XenServer release 7.0.0-125380c (xenenterprise)
[root@marshapjohnson ~]# exit
logout
Connection to 216.252.162.94 closed.

rklorese@rklorese-a01 ~ % ssh root@216.252.162.97
The authenticity of host '216.252.162.97 (216.252.162.97)' can't be established.
ED25519 key fingerprint is SHA256:/TgDZiTUM/GCzlrhcufzFkhrwOCZ4/DOUYxE+qEuWt0.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '216.252.162.97' (ED25519) to the list of known hosts.
root@216.252.162.97's password: 
Linux xoa 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64
 __   __             ____           _               _
 \ \ / /            / __ \         | |             | |
  \ V / ___ _ __   | |  | |_ __ ___| |__   ___  ___| |_ _ __ __ _
   > < / _ \ '_ \  | |  | | '__/ __| '_ \ / _ \/ __| __| '__/ _` |
  / . \  __/ | | | | |__| | | | (__| | | |  __/\__ \ |_| | | (_| |
 /_/ \_\___|_| |_|  \____/|_|  \___|_| |_|\___||___/\__|_|  \__,_|

Welcome to XOA Unified Edition, with Pro Support.

* Restart XO: sudo systemctl restart xo-server.service
* Display status: sudo systemctl status xo-server.service
* Display logs: sudo journalctl -u xo-server.service
* Register your XOA: sudo xoa-updater --register
* Update your XOA: sudo xoa-updater --upgrade

OFFICIAL XOA DOCUMENTATION HERE: https://xen-orchestra.com/docs/xoa.html

Support available at https://xen-orchestra.com/#!/member/support

In case of issues, use `xoa check` for a quick health check.

Build number: 21.08.23

Based on Debian GNU/Linux 11 (Stable) 64bits in PVHVM mode

Last login: Tue Apr 12 21:14:01 2022 from 216.252.162.112
[13:57 13] xoa:~$ exit
logout
Connection to 216.252.162.97 closed.

@olivierlambert @olivierlambert Merci, Olivier.

XenServer 7.0.0 (yes, I'll ask you about upgrading to XCP-ng one of these days real soon).

XOA is current.