NetTalk Central

NetTalk Web Server => Web Server - Ask For Help => Topic started by: Alberto on July 19, 2019, 09:28:20 AM

Title: New example 79 in 11.16, javascript error
Post by: Alberto on July 19, 2019, 09:28:20 AM

see pic

Title: Re: New example 79 in 11.16, javascript error
Post by: osquiabro on July 19, 2019, 12:07:23 PM

i have same error in NT 10.38..

Title: Re: New example 79 in 11.16, javascript error
Post by: Bruce on July 21, 2019, 10:06:32 PM

Open the Developer Tools in your browser,
go to the Console,
and see what the error says.

If necessary post a screen-shot of that please.

cheers
Bruce

Title: Re: New example 79 in 11.16, javascript error
Post by: Alberto on July 22, 2019, 05:08:53 AM

see pic

Title: Re: New example 79 in 11.16, javascript error
Post by: Bruce on July 22, 2019, 10:39:36 PM

hmm - what browser are you testing in?

cheers
Bruce

Title: Re: New example 79 in 11.16, javascript error
Post by: Alberto on July 24, 2019, 06:45:54 AM

firefox ok
chrome error

Title: Re: New example 79 in 11.16, javascript error
Post by: Bruce on July 24, 2019, 08:08:20 PM

what version of Chrome do you have installed?

Title: Re: New example 79 in 11.16, javascript error
Post by: Alberto on July 25, 2019, 04:51:17 AM

Versión 75.0.3770.100 (Build oficial) (64 bits)

Title: Re: New example 79 in 11.16, javascript error
Post by: Bruce on July 25, 2019, 07:05:53 PM

are you accessing the example using HTTPS?
if not, what URL are you using to access the example?

The only thing I can think of is that you are using the app on HTTP and so Chrome is complaining...
Everything else looks fine.

cheers
Bruce

Title: Re: New example 79 in 11.16, javascript error
Post by: Alberto on July 26, 2019, 05:51:04 AM

HTTP yes, 127.0.0.1:88
Why shoud I have to have https in my own box?
Or better asked:
How do I have to test this example?
May you please post the link to the webinar where you showed it?
Thanks

Title: Re: New example 79 in 11.16, javascript error
Post by: Bruce on July 28, 2019, 09:38:08 PM

>> HTTP yes, 127.0.0.1:88
>> Why should I have to have https in my own box?

You will have to ask Google that - that's their policy, not mine.

>> Or better asked:
>> How do I have to test this example?

You can make the connection to localhost secure (albeit with a warning message).
Just by using the certificates tab like any other secure site.

Personally I use a technique Jane Fleming demonstrated;
a) make a DNS entry pointing to your PC. (ie from the internet.)
In my case le3.capesoft.com - at the moment I did this the IP address was 197.242.203.124 (although it does not matter if this is variable.)
b) I opened port 80 in my router, and pointed it at the server on my machine.
c) I ran the "certificates" option on the server, so this went out and got a 90 day cert for le3.capesoft.com
d) I think _changed_ the DNS entry so that le3.capesoft.com now points to my LAN address (192.169.2.11)

Now I can go to le3.capesoft.com from any machine on my lan (including phones on wifi) and it comes out at my, completely secure, LAN server.

Of course it's only good for 90 days - if I wanted a longer cert I'd have to buy one.

>> May you please post the link to the webinar where you showed it?
https://www.capesoft.com/accessories/NetTalkUserGroup.htm 
#244

Cheers
Bruce