micahdg

@teraßyte I downgraded to php 8.1 and see the same results 😞 Great idea, though. @Stuart Silvester I see what you're talking about now - that 4.x reference means the requirements check isn't able to connect to the urls below, either. For some reason I thought I inadvertently resolved that issue a few days ago, but in fact I just hadn't refreshed the ips4.php file until after downgrading php to 8.1. I was able to get more precise google search results using "php8 file_get_contents Failed to open stream: Permission denied in" and found the suggestion that SELinux is causing the problem, so I executed the following two commands: These commands appear to give apache access to the network and internet. And now the install script can reach the license server 😄 So in the end, it was my own local security issue even though curls worked great. I confess I'm not super familiar with SELinux. Thank you for your patience and assistance! Hopefully this rabbit trail helps someone else in the future. This is all running on CentOS Stream 9, rhel 9 on a DigitalOcean vps.

I am the server administrator. There is no whitelist. Given what I've posted above, from my server I can POST to the license URL and get a response body. Additionally, the requirements checker here works well: Screenshot of the output is somewhere below. Two of the steps this requirements checker does includes hitting these two URLs: https://remoteservices.invisionpower.com/requirements https://remoteservices.invisionpower.com/updateCheck These are both successful. Any way to make the php output more of the error? It's sadly quite generic: "There was an error communicating with the IPS License Server. Please try again later or contact IPS technical support for assistance."

No cloudflare currently fronting the server, and I didn't pay for any WAF or ddos services yet. SELinux is enabled and the firewall is currently not installed.

Thank you, Marc. When I curl POST to that URL, I get this response body, which seems okay: The url matches the url I'm attempting to run the upgrade from (including the http vs https), and the same info matches in the conf_global.php. What's next? 😄

Sorry, I meant the infrastructure I use at two different hosts/datacenters/linux distros etc, in which the only real similarity between the two is that I rent them. I set up this newest one exclusively to gain access to php 8 for installing IB forums' latest version. I'm able to curl GET/PUT/POST from both servers to other companies' servers with successful responses. I'm able to connect and negotiate http2 and tls 1.2 but then get a 500 from invision's servers hosted or routed through cloudfront.net, presumably because I'm not offering the required query params or body: Is there a way to obtain what the whole request to https://remoteservices.invisionpower.com should look like? Query parameters, body, http method, etc? That would allow me (while inserting my own license key) to truly test this flow. Thank you for your patience and suggestions so far.

Thank you very much for the url. From my server I can ping, telnet, and get good nslookup data from the address. Do you know if this is something I can open a ticket for?

Can someone help me find the url that an Invision Community 4 upgrade license check hits to verify the license key? From multiple servers over multiple days and multiple copies of the 4.7.15 software, I always get "There was an error communicating with the IPS License Server. Please try again later or contact IPS technical support for assistance." I'd like to troubleshoot whether this url is being blocked by my infrastructure. Thanks for any pointers you can give me.