invisioncommunity.com.

You should be doing your checking against the following instead, as this is the FQDN of the endpoint the suite connects to...

remoteservices.invisionpower.com

 

You should be doing your checking against the following instead, as this is the FQDN of the endpoint the suite connects to...

remoteservices.invisionpower.com

This is not correct. invisioncommunity.com is the right domain for the Marketplace.

Test https/port 443 though. If that still fails you may want to do a tracert or something to figure out at what point the connection is failing.

OK - just basing it on the other outputs they have provided.

 

This is not correct. invisioncommunity.com is the right domain for the Marketplace.

Test https/port 443 though. If that still fails you may want to do a tracert or something to figure out at what point the connection is failing.

I tested port 443 and it fails to determine the route, like I posted before.

root@ecne:/home/thebores/public_html# nmap --script ssl-enum-ciphers -p 443 invisioncommunity.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-06-28 15:58 CDT
setup_target: failed to determine route to invisioncommunity.com (13.226.204.116)
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.35 seconds

 

 

This is not correct. invisioncommunity.com is the right domain for the Marketplace.

Test https/port 443 though. If that still fails you may want to do a tracert or something to figure out at what point the connection is failing.

remoteservices.invisioncommunity.com routes via port 443, but not invisioncommunity.com by itself.

root@ecne:/home/thebores/public_html# nmap --script ssl-enum-ciphers -p 443 remoteservices.invisioncommunity.com
Starting Nmap 7.80 ( https://nmap.org ) at 2023-06-28 16:01 CDT
Nmap scan report for remoteservices.invisioncommunity.com (18.154.219.51)
Host is up (0.0024s latency).
Other addresses for remoteservices.invisioncommunity.com (not scanned): 18.154.219.7 18.154.219.78 18.154.219.50 2600:9000:250e:9200:16:1470:7d40:93a1 2600:9000:250e:d000:16:1470:7d40:93a1 2600:9000:250e:e200:16:1470:7d40:93a1 2600:9000:250e:a800:16:1470:7d40:93a1 2600:9000:250e:7200:16:1470:7d40:93a1 2600:9000:250e:9600:16:1470:7d40:93a1 2600:9000:250e:7c00:16:1470:7d40:93a1 2600:9000:250e:f800:16:1470:7d40:93a1
rDNS record for 18.154.219.51: server-18-154-219-51.dfw56.r.cloudfront.net

PORT    STATE SERVICE
443/tcp open  https
| ssl-enum-ciphers: 
|   TLSv1.2: 
|     ciphers: 
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (ecdh_x25519) - A
|     compressors: 
|       NULL
|     cipher preference: server
|_  least strength: A

Nmap done: 1 IP address (1 host up) scanned in 0.67 seconds

 

Nothing on my server has changed. The Marketplace worked in my control panel back in February and now is doesn't. Any ideas?

Guys, this appears to be the only customer support option open to me. Can you give me some assistance with this?

Please use tracert to that URL as mentioned by my colleague. That will give you a clearer indication of where exactly its stopping

 

Please use tracert to that URL as mentioned by my colleague. That will give you a clearer indication of where exactly its stopping

To what url?

If I traceroute from my server to invisioncomunity.com, I get this:

traceroute invisioncommunity.com
traceroute to invisioncommunity.com (13.226.204.57), 30 hops max, 60 byte packets
connect: Invalid argument

If I traceroute to remoteservices.invisioncommunity.com (I am just guessing that this is the URL in question), I get:

traceroute remoteservices.invisioncommunity.com
traceroute to remoteservices.invisioncommunity.com (18.154.219.7), 30 hops max, 60 byte packets
 1  unassigned-ip-vivawebhost.com (72.249.68.206)  0.515 ms  2.292 ms  2.234 ms
 2  207.210.228.49 (207.210.228.49)  2.196 ms  2.121 ms  2.070 ms
 3  xe-402.jbdr-01.dal.tierpoint.net (206.123.64.153)  2.022 ms  1.979 ms xe-403.jbdr-01.dal.tierpoint.net (206.123.64.24)  1.941 ms
 4  te0001.corertr-01.da2.tierpoint.net (206.123.69.162)  5.075 ms  5.033 ms  4.991 ms
 5  te0020.brdrrtr-01.da2.tierpoint.net (173.237.128.19)  4.947 ms  4.881 ms  4.847 ms
 6  ipv4.de-cix.dfw.us.as16507.amazon.com (206.53.202.34)  4.796 ms  2.038 ms  4.220 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  15.230.157.24 (15.230.157.24)  1.882 ms 15.230.157.25 (15.230.157.25)  1.829 ms 15.230.157.24 (15.230.157.24)  2.814 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

 

The last number I get a return from is an Amazon IP. You folks appear to host with Amazon. The problem does not look like it is on my end.

Any ideas?

Thank you for this thread it helped me out so I thought I would post what fixed for me in case it helps anyone else.

The TLS 1.2 was the issue for me, but was because of CloudFlare, my TLS for CloudFlarewas set to 1.3 minimum, changed back to 1.2 and the marketplace works again.

 

Any ideas?

My colleague has this down to take a look at, however please bear in mind we are currently closed for the holidays.

 

My colleague has this down to take a look at, however please bear in mind we are currently closed for the holidays.

OK. I'll check back. Thanks.

Another week has passed. Have you guys figured anything out?

Sorry for the delay. I will get a ticket on this for you, so we can look into this further.

 

Sorry for the delay. I will get a ticket on this for you, so we can look into this further.

Thanks.

The Marketplace is now working in my admin area. Nothing changed on my end, so I assume you folks changed something on your end. Thanks for the help.

Nothing at all on our end, but glad to see its working regardless. Please let us know if you have any further issues

Someone fixed something somewhere and the routing issue was beyond my network and out of my control. All's well that ends well though, I guess. Thanks again.

No problem at all 🙂

And I am once again getting the '3C409/3' error. Nothing has changed on my end. There were no changes on my end before it stopped working. No changes before it started working. There have been no changes and it stops working again. This is getting ridiculous.

Sorry to hear you are having issues. I will get someone to take a look at this as soon as possible.

And it's working again. I haven't touched a setting on my server in months. Nothing is changing on my end. I would love to know what is changing elsewhere to cause this.

 

And it's working again. I haven't touched a setting on my server in months. Nothing is changing on my end. I would love to know what is changing elsewhere to cause this.

We changed something our end, which has resolved this

And the error is back again!