http://coldfusion.com logo
Join Slack
Powered by
Next one. On a secured server that will not allow...
# lucee
a
Next one. On a secured server that will not allow Lucee's attempts to phone home, the Lucee server admin extensions page (path: /lucee/admin/server.cfm?action=ext.applications) won't even load, instead returning a 404. This is on 5.4.1.8 I get that it won't be able to phone home to get... I dunno... a list of possible extensions?... but the page should still work and tell me what extensions I've actually got, right?
z
wanna contribute a fix?
a
Pretty much got my hands full with the issues all this is causing on my end ATM, if I'm honest.
Seems odd that a "phone home" being done during rendering a page causes a 404 of the whole page though yeah?
z
yes and no, let me see what i can do-ski
a
don't sweat it mate. I'm just trying to troubleshoot the other thing I raised about the extensions.
I can raise a ticket for this though?
z
what's the stack / error?
i'm getting this with wifi turned off
a
I'm literally getting an nginx 404
(after quite a long delay)
I guess could just be the web server giving up too soon
but a 404 is odd, rather than a 504
z
long being 50s?
a
(this is the nginx install that comes with the lucee/lucee:5.4.1.8-nginx)
Ah I mean if Nginx gives up on the upstream service, I'd expect it to give a 504, not a 404
z
yeah
(digging)
10s wait more or less?
yeah i think i know what's going on, it's a redux of https://luceeserver.atlassian.net/browse/LDEV-1358
a
Around that. yeah
Yeah and sounds like that
z
hmm, what does the 404 response look like?
i only see a header="404" on the detail page
a
It's literally Nginx's 404 page.
Copy code
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
and so if you send a 404 header... this is what the web server will do with it
z
don't suppose you can access the port 8888 version to bypass nginx can u?
a
Don't have port 8888 open sorry And can't be arsed working out how to login to admin using curl on the server 😉
z
something else you could do to help me, as i can't repo this, could you do a cfhttp on that server to the update server url and dump the response out? I can't reproduce this firewall stuff locally with wifi turned off
that way i can improve the error handling in the admin?
a
Yep, maybe I can do both later this afternoon
z
awesome
a
I have a coupla releases to get out this afternoon before it gets too close to beer o'clock (not that I can have beer this evening...)
z
deploy friday!!!
a
yeah. It depends on the release, but we're not afraid of Fridays. Until like 4pm or so
This "Lucee needs to phone home to finish an installation" thing is biting us again. What's the phone-home IP address (IP ADDRESS)? I need to open it on one of our servers. <---- THIS IS THE IMPORTANT PART OF THE QUESTION I'm also thinking of raising a ticket to get the situation improved that if Lucee can't phone home, then it logs something to that effect. Rather than just symptoms of the phone-home failure eg "In the OSGi Bundle with the name [esapi.extension] and the version [2.2.4.7] was no class with name [org.lucee.extension.esapi.functions.EncodeForHTML] found"
I note in another thread the 
<https://ext.lucee.org>
. Is that what the phone-home code is calling too: 
<http://ext.lucee.org|ext.lucee.org>
? Is it on a static IP? (looks like a cloudfront host, so I'm guessing not...)
3 Views
Open in Slack
PreviousNext
Powered by