Please ensure you have the latest version of the plugin installed.

Via your server webGUI go to the Plugins page. For "My Servers" you should see version 2022.09.28.1258

 

If you've confirmed you're on the latest version, please provide the following details

1. Your Diagnostics zip download (webGUI > Tools > Diagnostics)
2. Open an Unraid terminal and execute the command below then provide the output

   unraid-api report -v

Hi, i got the same Problem. For some reason the WAN Port was switched back to 443 after upgrading. i changed it back, now the CHECK does not fail anymore.

 

but still the same problem as above.

 

Here is my diagnostic and output of that command:

 

 

 

krx-nas-diagnostics-20221003-2239.zip

Hi everybody,

I have the same issue...  

 

.. and my diagnostic output:

 

 

And as above, I have the same error message displayed.

 

API Report:

<-----UNRAID-API-REPORT----->
SERVER_NAME: Zen
ENVIRONMENT: production
UNRAID_VERSION: 6.10.3
UNRAID_API_VERSION: 2.52.1 (running)
NODE_VERSION: v18.5.0
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: Bebbo
CLOUD: ok [IP=52.40.54.163]
RELAY: connected
MINI-GRAPH: connected
ONLINE_SERVERS: Zen[owner="Bebbo"]
OFFLINE_SERVERS:
ALLOWED_ORIGINS: http://localhost, http://IPV4ADDRESS, https://IPV4ADDRESS, http://zen, https://zen, http://zen.local, https://zen.local, https://HASH.unraid.net
HAS_CRASH_LOGS: yes
</----UNRAID-API-REPORT----->
<-----UNRAID-API-CRASH-LOGS----->
PID 13291 received SIGSEGV for address: 0x0
/tmp/pkg/85fc9a0e8a73534c4faeec0ec66b716757255ef4d0559b9473aed94f84658b19/segfault-handler/build/Release/segfault-handler.node(+0x37a5)[0x145f065a67a5]
/lib64/libpthread.so.0(+0x123a0)[0x145f062143a0]
/usr/local/sbin/unraid-api(_ZN2v88internal18MarkingVisitorBaseINS0_24ConcurrentMarkingVisitorENS0_22ConcurrentMarkingStateEE23ProcessStrongHeapObjectINS0_18FullHeapObjectSlotEEEvNS0_10HeapObjectET_S7_+0x27)[0x13675c7]
/usr/local/sbin/unraid-api(_ZN2v88internal17ConcurrentMarking3RunEPNS_11JobDelegateENS_4base7EnumSetINS0_13CodeFlushModeEiEEjb+0x4598)[0x136d9f8]
/usr/local/sbin/unraid-api(_ZN2v88internal17ConcurrentMarking7JobTask3RunEPNS_11JobDelegateE+0xa0)[0x136fee0]
/usr/local/sbin/unraid-api[0xe57b3c]
/usr/local/sbin/unraid-api[0xa7191c]
/lib64/libpthread.so.0(+0x7e45)[0x145f06209e45]
/lib64/libc.so.6(clone+0x3f)[0x145f0612e4af]
PID 3112 received SIGSEGV for address: 0x0
/tmp/pkg/85fc9a0e8a73534c4faeec0ec66b716757255ef4d0559b9473aed94f84658b19/segfault-handler/build/Release/segfault-handler.node(+0x37a5)[0x14564043b7a5]
/lib64/libpthread.so.0(+0x123a0)[0x1456400a93a0]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal6String11WriteToFlatIhEEvS1_PT_iiNS0_16PtrComprCageBaseERKNS0_31SharedStringAccessGuardIfNeededE+0x58)[0x1671f38]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal6String11WriteToFlatIhEEvS1_PT_ii+0x19)[0x16721a9]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal6String11SlowFlattenEPNS0_7IsolateENS0_6HandleINS0_10ConsStringEEENS0_14AllocationTypeE+0x240)[0x1672410]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal7Factory18NewProperSubStringENS0_6HandleINS0_6StringEEEii+0x564)[0x1388db4]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal23Runtime_StringSubstringEiPmPNS0_7IsolateE+0x5a)[0x1792aaa]
/usr/local/bin/unraid-api/unraid-api[0x1bb6239]

<-----UNRAID-API-CRASH-LOGS----->

 

System diagnostic attached.

zen-diagnostics-20221004-1308.zip

Hi @KrX @OlejoHome @Bebbo, 

 

This sounds like a CORS error, are you using a reverse proxy? Those are not currently supported.

 

If you look at the ALLOWED_ORIGINS area of the `unraid-api report -v` command that you ran it will show you the list of URLs that the system will accept. Only URLs listed there will work with My Servers.

13 hours ago, ljm42 said:

Hi @KrX @OlejoHome @Bebbo, 

 

This sounds like a CORS error, are you using a reverse proxy? Those are not currently supported.

 

If you look at the ALLOWED_ORIGINS area of the `unraid-api report -v` command that you ran it will show you the list of URLs that the system will accept. Only URLs listed there will work with My Servers.

 

Im not using and reverse proxy. this happened after upgrading to 6.11.0 from 6.10.3

I also get the same error:
report unraid-api -v
Generating report please wait...
<-----UNRAID-API-REPORT------>
SERVER_NAME: NAS
ENVIRONMENT: production
UNRAID_VERSION: 6.11.0
UNRAID_API_VERSION: 2.50.0 (running)
NODE_VERSION: v18.5.0
API_KEY: valid
MY_SERVERS: authenticated
MY_SERVERS_USERNAME: *********
CLOUD: offline
RELAY: disconnected
MINI-GRAPH: disconnected
ONLINE_SERVERS:
OFFLINE_SERVERS:
SOURCES_ALLOWED:
HAS_CRASH_LOGS: yes
</----UNRAID-API-REPORT----->
<-----UNRAID-API-CRASH-LOGS------>
PID 5557 received SIGSEGV for address: 0x10
/tmp/pkg/85fc9a0e8a73534c4faeec0ec66b716757255ef4d0559b9473aed94f84658b19/segfault-handler/build/Release/segfault-handler.node(+0x37a5)[0x1499c224e7a5]
/lib64/libc.so.6(+0x3a6a0)[0x1499c1d576a0]
/lib64/libc.so.6(+0x9a47a)[0x1499c1db747a]
/lib64/libc.so.6(malloc+0x9a)[0x1499c1db86ba]
/usr/lib64/libstdc++.so.6(_Znwm+0x1c)[0x1499c20d262c]
/usr/local/bin/unraid-api/unraid-api(_ZN6v8impl9Reference3NewEP10napi_env__N2v85LocalINS3_5ValueEEEjbPFvS2_PvS7_ES7_S7_+0xb3)[0x9b3af3]
/usr/local/bin/unraid-api/unraid-api(napi_create_reference+0x8c)[0x9b9a5c]
/usr/local/bin/unraid-api/build/libvirt.node(_ZN10Hypervisor19DomainGetUUIDStringERKN4Napi12CallbackInfoE+0x1a9)[0x1499c013f6b9]
/usr/local/bin/unraid-api/build/libvirt.node(_ZN4Napi10ObjectWrapI10HypervisorE29InstanceMethodCallbackWrapperEP10napi_env__P20napi_callback_info__+0x10a)[0x1499c012ccda]
/usr/local/bin/unraid-api/unraid-api[0x9bd45c]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal25FunctionCallbackArguments4CallENS0_15CallHandlerInfoE+0x121)[0x1238481]
/usr/local/bin/unraid-api/unraid-api[0x1238df3]
/usr/local/bin/unraid-api/unraid-api(_ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE+0xf7)[0x12392d7]
/usr/local/bin/unraid-api/unraid-api[0x1bb6339]

SOLVED: Error resolve dns

On 10/7/2022 at 11:40 PM, ljm42 said:

This sounds like a CORS error, are you using a reverse proxy? Those are not currently supported.

 

Saw this response in a different thread as well. Is it even planned to be supported some time in the future? Or is there an "unsupported" way to modify ALLOWED_ORIGINS?

On 10/9/2022 at 8:31 AM, sn0opy said:

 

Saw this response in a different thread as well. Is it even planned to be supported some time in the future? Or is there an "unsupported" way to modify ALLOWED_ORIGINS?

 

I expect it will be coming in the future.