Cfhttp DNS issues on Debian

dev
1

disclaimer: mostly windows guy with just moderate linux experience

I have a new debian 12/lucee 6.2.1.122 vm running

From the vm console name resolution works fine. Pinging cbc.ca returns cbc.ca (23.37.212.2)

but when I try to cfhttp cbc.ca I get a “Temporary failure in name resolution” error. This occurs with any url.

Any ideas on why that might be happening and how to fix?

2

that’s odd, works fine on trycf with all versions and for me locally.

you are using the installer version with java 21 yeah?

3

I’m afk but I used the stable Linux installer with all defaults so I assume yes.

The Temporary failure message seems to be pretty Linux specific so I’ve probably got something mucked up in debian but not understanding why console works but cfhttp doesn’t.

4

But i can repo on my radxa-zero3E SBC from cfcamp

<cfscript>
	dump(server.os);
	dump(server.lucee);
	//dump(server.java);

	http url="cbs.ca" result="result";
	dump(result);
</cfscript>

image
image525×791 16.2 KB

5

Maybe because CBS.ca is domain parked?

It’s cbC.ca that I used.

6

ahhh, doh!

cbc.ca works fine for me

image

Even the redirect logging now works :slight_smile:

7

Speaking of doh…

I rebooted the VM…and it works. I must have made some config change (I’m doing a lot of that as I move off of windows) that needed a refresh.

BTW…this is code for my Bluesky weather alert bots that use Lucee to parse Environment Canada weather alert public data because there is no official presence on Bluesky yet. There’s 1 for each weather region in Canada. A fun Lucee use case.

ie: @skwxalerts.bsky.social on Bluesky

1 Like
8

it might have been a pooled connection?

If you encounter it again, try this?

9

I did see a post here recommending adding pooled=“false” and added that but it didn’t seem to make a difference.

Thanks for your help.

10

Went right to debian from windows, not via Ubuntu on the learning curve… brave man :wink:

did you go apache or nginx out of interest?

11

*headless Debian :smirk:

I have used Debian in the past (at my old job I set up an IDS using Debian, had Debian/gnome as a desktop for a while and had a Linux VPS for our website for several years. etc) it’s just been a while. But it is coming back.

I went Apache because it’s what I’ve used before. (And none of my websites need nginx performance)

1 Like