Frontplate Web to local https server fails because certificate error

Frontplate Web to local https server fails because certificate error

stephan_auerbachJXP4V
Observer Observer
769 Views
7 Replies
Message 1 of 8

Frontplate Web to local https server fails because certificate error

stephan_auerbachJXP4V
Observer
Observer

Try this: 

"https://localhost:8888"

 

in Chrome it's OK

 

But loading  it as Frontplatte URL gives an 

ERR_CERT_COMMON_NAME_INVALID error

0 Likes
770 Views
7 Replies
Replies (7)
Message 2 of 8

Christian_Garimberti
Advisor
Advisor

Hi, but "https://localhost:8888" is Vred itself via his webserver? Or another service?

 

Best

Chris

Christian Garimberti
Technical Manager and Visualization Enthusiast
Qs Informatica S.r.l. | Qs Infor S.r.l. | My Website
Facebook | Instagram | Youtube | LinkedIn

EESignature

0 Likes
Message 3 of 8

YES!

At least should show this (s. Picture).

... and sure, the regular browser will initially complain, but there is a dialog to ignore the certificate or security problem, and then it works until you clear the cache.
[cid:[email protected]]
Of course the regular Browser complains
0 Likes
Message 4 of 8

Christian_Garimberti
Advisor
Advisor

Hi, no image attached but, are you trying to create an infinite loop?

or it is from different instance of Vred?

I don't think Vred webserver could be used as part of the same Vred session (itself). But I never tried

 

Best

Chris

Christian Garimberti
Technical Manager and Visualization Enthusiast
Qs Informatica S.r.l. | Qs Infor S.r.l. | My Website
Facebook | Instagram | Youtube | LinkedIn

EESignature

0 Likes
Message 5 of 8

NO,NO, thats no infinite loop.
It just shows that custom web-server with no official certificate (like the localhost:8888 is one ) got the certificate issue.
It's just an example to show that problem.
Of course you should not stream anything ..
Only the main page !!

0 Likes
Message 6 of 8

Christian_Garimberti
Advisor
Advisor

I suppose the certificate error is coming from that specific source page. I tried with this page and it works.

Have you tried with other pages?

Christian_Garimberti_0-1732897049307.png

and trying your test a got a certificate error also in Chrome

Christian_Garimberti_1-1732897282287.png

 

Best

Chris

 

Christian Garimberti
Technical Manager and Visualization Enthusiast
Qs Informatica S.r.l. | Qs Infor S.r.l. | My Website
Facebook | Instagram | Youtube | LinkedIn

EESignature

0 Likes
Message 7 of 8

Hi,

That's the point. Official Webpages with a valid certificate, are no problem.
Custom https servers like your own "localhost:8888" do never have an official certificate .
(It only guarantees secure data exchange. )
If you open such a custom https server with Chrome you get a warning, yes!
But you can manually trust your own server !!
The VRED Chromium does not have this dialog!
So, you can't allow your own https server.

0 Likes
Message 8 of 8

 

"Oops, I just realized that when I click on REPLY, I am not logged in and therefore cannot upload images, very strange...

 

Never mind...

 

When I edit a front plate with "https://localhost:8888 ", I expect to get the same dialog as in normal browsers (Chrome).

 

d1.PNG
Clicking on the button expands to
d2.PNG
then clicking on the link "localhost" and voilà
that's what I want to achieve.

 

d3.PNG

 

This is just an example for a local https service, which almost never has an official certificate:
The only thing missing in the VRED front plate is the dialog (see images).
Instead, it just doesn't accept it.
 
There are two ways to solve this:
 
1. Allow https with unofficial certificates in general through a preference setting (preferred)
2. Apply the dialog as in normal browsers

 


 
 
 

 

0 Likes