Jump to content

DonnonGT

Clients
  • Posts

    47
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by DonnonGT

  1. 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.

  2. 8 hours ago, Marc Stridgen said:

    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  * * *

     

  3. 1 minute ago, Stuart Silvester said:

    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

     

    2 minutes ago, Stuart Silvester said:

    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

     

  4. 1 minute ago, Stuart Silvester said:

    The TLS version only matters for the login in process where our servers are sending data to your server.

    This error is a communication error without outgoing requests from your server to our Marketplace. I would make sure that your server can communicate with invisioncommunity.com, you could check this from command line, or ask your web host to if you're not sure how to.

    Starting Nmap 7.80 ( https://nmap.org ) at 2023-06-28 15:34 CDT
    setup_target: failed to determine route to invisioncommunity.com (13.226.204.59)
    WARNING: No targets were specified, so 0 hosts scanned.
    Nmap done: 0 IP addresses (0 hosts up) scanned in 0.35 seconds

    4 minutes ago, Stuart Silvester said:

    The TLS version only matters for the login in process where our servers are sending data to your server.

    This error is a communication error without outgoing requests from your server to our Marketplace. I would make sure that your server can communicate with invisioncommunity.com, you could check this from command line, or ask your web host to if you're not sure how to.

    Here is an attempt to load that URL using wget:

    root@ecne:/etc/apache2/sites-available# wget invisioncommunity.com
    --2023-06-28 15:36:40--  http://invisioncommunity.com/
    Resolving invisioncommunity.com (invisioncommunity.com)... 2600:9000:2031:7c00:1b:50ae:d340:93a1, 2600:9000:2031:3800:1b:50ae:d340:93a1, 2600:9000:2031:f000:1b:50ae:d340:93a1, ...
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:7c00:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:3800:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:f000:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:9800:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:2000:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:d600:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:0:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|2600:9000:2031:b200:1b:50ae:d340:93a1|:80... failed: Network is unreachable.
    Connecting to invisioncommunity.com (invisioncommunity.com)|13.226.204.59|:80... failed: Invalid argument.
    Connecting to invisioncommunity.com (invisioncommunity.com)|13.226.204.57|:80... failed: Invalid argument.
    Connecting to invisioncommunity.com (invisioncommunity.com)|13.226.204.116|:80... failed: Invalid argument.
    Connecting to invisioncommunity.com (invisioncommunity.com)|13.226.204.86|:80... failed: Invalid argument.

    I am able to fetch other webpages using wget, just not invisioncommunity.com.

  5. Just now, Jim M said:

    Unfortunately, at this point in time TLS 1.2 is required.

    TLSv1.2 and TLSv1.3 are both enabled on my server. They were both enabled when I was able to access the Marketplace and they are both enabled now, when I no longer can. Nothing on my end changed. I let my membership last and just renewed it today. Is there any chance that that is why I can't access the Marketplace?

    18 minutes ago, Jim M said:

    Unfortunately, at this point in time TLS 1.2 is required.

    And for what it's worth, my server is connecting to your server using TLSv1.2:

    Nmap scan report for remoteservices.invisionpower.com (18.154.219.7)
    Host is up (0.0023s latency).
    Other addresses for remoteservices.invisionpower.com (not scanned): 18.154.219.50 18.154.219.51 18.154.219.78 2600:9000:250e:8200:16:1470:7d40:93a1 2600:9000:250e:b800:16:1470:7d40:93a1 2600:9000:250e:4e00:16:1470:7d40:93a1 2600:9000:250e:f600:16:1470:7d40:93a1 2600:9000:250e:2000:16:1470:7d40:93a1 2600:9000:250e:9c00:16:1470:7d40:93a1 2600:9000:250e:7e00:16:1470:7d40:93a1 2600:9000:250e:2a00:16:1470:7d40:93a1
    rDNS record for 18.154.219.7: server-18-154-219-7.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.65 seconds

     

  6. I am once again getting the '3C409/3' configuration error when I click on the Marketplace link on my control panel. I am running TLS version 1.3. I have the following IP subnet whitelisted: 108.220.132.0/24.  Any ideas what else might be causing this error? Thanks.

  7. Hello. I am having this same issue. When I click on the Marketplace link in my control panel, I get the following error:

    3C409/3 There was an error communicating with the Marketplace server. Please try again later, or contact us for assistance.

    This doesn't appear to be an issue with my firewall. There are four A records pointing at invisioncommunity.com, all with IP numbers on the same class C subnet. I have whitelisted that subnet. I whitelisted the subnet of another class C subnet with 4 IP numbers that point to remoteservices.invisionpower.com as well, just in case. I still get the error.

    I have watched my server's log files while I attempted to connect to the Marketplace in my control panel and nothing is being blocked on my end. I have been unable to connect to the Marketplace for several months. I was running an older version before and assumed that was the reason I could not connect. I upgraded last month to v4.7.5 and nothing changed. I still cannot connect. Any ideas?

  8. 2 hours ago, batarjal said:

    You can change it easily yourself so you don't have to wait
    It's just one template adjustment under:

    ACP > Customization > Appearance > Themes > Edit HTML and CSS </> > Search for threadstarterimage

    tareget_blank.thumb.png.80aaab0f4e981c25d86056f8fc2dcb00.png

    I appreciate the advice on this, but this doesn't appear to be the area that builds the links in question. I am referring to the thumbnail links to the actors in a given movie, or to movie credits to a given actor. I've included a pic below. These thumbnail links link to the current window the site occupies.

    1244650163_ScreenShot2021-07-11at5_43_59PM.thumb.png.98aa3fd6aae0d969d3752a1d4bb78c1f.png

    1872687526_ScreenShot2021-07-11at5_49_23PM.thumb.png.91cb5952b1f6ddb091bda3dae7fd3d2d.png

  9. 2 hours ago, batarjal said:

    You can change it easily yourself so you don't have to wait
    It's just one template adjustment under:

    ACP > Customization > Appearance > Themes > Edit HTML and CSS </> > Search for threadstarterimage

    tareget_blank.thumb.png.80aaab0f4e981c25d86056f8fc2dcb00.png

    Outstanding. I appreciate the information. I'll change it on my end. Thanks again.

  10. 17 minutes ago, batarjal said:

    I agree that it should open in a new tab, I'll add that to the next update.


    I'm not sure if changing a review is possible, I reported it and linked to your post.

    Hello. Can you tell me when the next update will be? I'm not keen on running this app until this is addressed. Thanks.

×
×
  • Create New...