Bug: cpanel html editor not linking directory images big red "X".

[jeffschips]

CENTOS 7.7 kvm v84.0.21

Anybody have a solution to cpanel html editor not displaying .jpg, .png, .gif images in the editor and showing a big red "X" when importing images into an .html page? I brought this up with tech support and they confirmed on their end that this is an issue as well but I find it odd such an important feature remains unresolved. And this has only happened recently. I've been using the cpanel html editor for years with no problem. Here is how it happens:

Login into cpanel, navigate to a directory with an html web pages. Create an html page and attempt to import an image using the cpanel html editor for images. Remember, the actual images are located in the same directory as the html page - yet nothing shows, just a big red "X" indicating the image is not being imported.

I've checked that all permissions are proper 755 for directory and 644 for image files. Even changing the directory to 750 doesn't change the issue. I've checked source of html page and paths are correct.

This is truly odd.

 

[cPanelLauren]

Can you give me more precise steps to replicate this or a case ID if it's a known issue?
I went to cPanel>>File Manager->public_html for my domain -> Selected an HTML File -> HTML Editor -> Clicked the "Image" button -> Upload Image -> Selected my Image and uploaded it and I'm not seeing any issue with the image I uploaded.

 

[jeffschips]

Hi and thanks for the quick response! Appreciate that. The case ID is CPANEL-31403. I did the exact same steps you have and I only get the red X. Of note, when working in this directory I can, for some reason, succesfully import images from a subdomain of the domain I'm working with but not from within the main domain. Very strange.

 

[cPanelLauren]

Hi @jeffschips

There's actually a comment in the case about the hostname that is interesting. Uunfortunately your ticket is the only one that is added to this case right now - though it was just opened yesterday.

One of the PO's noted that they were only able to reproduce this in the event the hostname of the server didn't resolve (most of our test environments don't actually have working hostnames/domains) - he noted that when they put the hostname in their local /etc/hosts/ file (local hosts file) the issue was resolved. This would explain why the analyst was able to replicate the behavior as well.

They did note that either way it's an issue and should be resolved but it could be a direction to explore?

I see your hostname resolves but I wonder if there isn't some further resolution related issue involved occurring on the server itself.

 

[jeffschips]

Wow that's interesting. So you are suggesting I put the domain name in my server's /etc/hosts file? And why in the first place wouldn't this TLD resolve anyway, I'm wondering.

 

[cPanelLauren]

I'm sorry, no I'm not suggesting that, I was just explaining the full situation. I was saying that internally (here) most of our hostnames don't resolve (at least on our test environments), in order to work around this we have to add our hostnames/domains to our local hosts file.

The server the analyst was using and the server that the development team used to replicate your issue both had non-resolving hostnames.

The product owner for the team employed the workaround of adding the hostname of his test environment to his own local hosts file and found that the image preview began to work.

I checked your DNS for the hostname externally it looks great. What I was suggesting was that in light of that information, ensuring that locally DNS resolution is functioning normally.

 

[jeffschips]

Ah okay I see. Thanks for clearing that up. I'll check into that. Strange that, though, it works locally when the links to images references a directory *outside* the one with the images. . .

 

[cPanelLauren]

Ah okay I see. Thanks for clearing that up. I'll check into that. Strange that, though, it works locally when the links to images references a directory *outside* the one with the images. . .

I agree fully! It doesn't make a lot of sense and actually I was curious about something - if you use the developers tools in chrome or firefox (or whichever browser) where does the URL point for the image? What URL are you using to access your cPanel UI?

 

[jeffschips]

Excellent idea using the developers too! I hadn't thought of that . Brilliant! I'll try it out and report back.

 

[jeffschips]

Dude! You're the dude! Using web developer has revealed the issue but frankly, I don't know how to resolve it. So, when loading an image web developer shows a 404 error with the following link, which obviously is wrong (the domain names have been changed but you will get the idea):

https://domain1.com.cpanel-account-domain-name.com/domain1.com/archives/image.jpg

When it works it should show the link as follows:

https://domain1.com/archives/image.jpg

Don't know why cpanel is pre-pending a mash-up with the following domains/link:

domain1.com.cpanel-account-domain-name.com

Maybe you have a clue but this is definitely the reason why this is occurring - wrong domain request.

 

[cPanelLauren]

Dude! You're the dude!

lol

Don't know why cpanel is pre-pending a mash-up with the following domains/link:

domain1.com.cpanel-account-domain-name.com

Does it actually look like this: https://domain1.com/~$USER/ or does it look like a really long subdomain as posted?

 

[clarkfilio]

hello, was there any solution to this issue? I'm having the exact same problem and GoDaddy customer service is having a hard time helping me

 

[cPRex]

@clarkfilio - it seems the original issue was a problem with the server's hostname. Does the hostname on your server resolve properly in DNS?

 

[clarkfilio]

@clarkfilio - it seems the original issue was a problem with the server's hostname. Does the hostname on your server resolve properly in DNS?

I'm out of my depth with that, I wouldn't know how to check if the hostname on my server resolves properly in DNS. Everything else is working fine from what I can tell, this is the only problem I'm experiencing, exactly as OP described.

 

[cPRex]

@clarkfilio - it sounds like you only have cPanel access to the machine, and not root access to the entire server. If that's the case, you'll have to continue to work with GoDaddy to have them troubleshoot the issue, as you just wouldn't have the access necessary to do any work on your end.