app.run(host='0.0.0.0',port=443,threaded=True,ssl_context=(
'certs/mydomain.com_bundle.crt',
'certs/mydomain.com.key'),debug=False)
This is my code in flask.
The strange things is, I can use PCs like MAC OS and WINDOWS to enter the website using HTTPS, no warnings at all and all certificates are shown as secured. But I just can't enter it using my mobile devices like my phone and my android tablet. Haven't tried iPad or iPad pro yet cause I don't have one.
All errors are "REFUSED TO CONNECT". That seems pretty much to be a problem in the program.
However if I switch it to HTTP & PORT=80 , I can enter it using basically all devices.
So does anyone know how to allow mobile devices to enter it using HTTPS as well?
My bad.
For some unknown reasons, my phone's browser didn't use HTTPS, it used HTTP as url proxy instead.
In the best of my knowledge, most browsers set HTTPS as the first priority for connections, yet the chromes in both of my mobile devices used HTTP, so did the default browsers...
So changing the url proxy to HTTPS fixed the problem, just that simple.
Related
I am trying to create a webpage that will be available for my team members. From my personal laptop.
Today i created a basic page using following tutorial.
https://www.interserver.net/tips/kb/how-to-create-website-in-iis/
But when i tried to open the page from another pc...
It didnt work.
I have added port 80 in firewall setting.
When i tried to open using my mobile.it worked. Because my laptop is connected to mobile hotspot.
But showing error as site cant be reach on outside devices.
Please help me.
Do i need to do port forwarding??? If yes then how can i do it on mobile?
As right now i can use only mobile hotspot
.
Pc OS : windows 10.
I have enabled IIS using windows feature
Is it necessary to install windows server? To be able to publish page to outside user?
It is unnecessary to install windows server to host websites. IIS also works in Windows Client OS.
If your mobile could access the website correctly, there are might be something wrong with network connectivity causing the failure of accessing the webpage from other PC. We should ensure that the other PC is in the same network with the webserver(your laptop), just like the network of your mobile.
I advise other PC to join the mobile hotspot too. Following shutting the firewall and access the website by using the IP address again.
Considering the Ping tool to troubleshoot the network issue.
https://www.hellotech.com/guide/for/how-to-do-a-ping-test-windows-10
Feel free to let me know if there is anything I can help with.
I've created my LocalHost using Node.js to test and debug my javascript project.
I'm Using Chrome.
On HTTPS server I need to click allow using mic just the first time, but in my localhost, I need to click on allow pup op each time my project calls microphone.
How do I allow access to my microphone on my localhost once?
If there is not a way to achieve that do you know any free https hosting fo testing purposes...
You need a secure connection in order for Chrome to remember your permission preference. You should be able to create a self-signed cert (the instructions differ based on the OS) so that you can actually visit localhost securely, once you've done that your microphone will be accessible between page loads.
I've written a non-published (personal) Chrome extension that performs page checking and then performs actions such as opening new tabs if certain conditions are met. I would like to be able to "remote control" it from my phone though, e.g. turn on or off or adjust settings when I'm away from my desk.
I considered if the extension can read/write to a file in Dropbox, which I could then edit from my phone too, or any other device. But I'm not sure if extensions are allowed to arbitrarily read/write in the filesystem, or only "apps". Any other suggestions?
Assuming you can't directly connect to your computer (otherwise wOxxOm's answer is valid)..
You could make a companion phone app and use GCM push messages; your phone would message your server via it (which can be hosted on a free App Engine tier easily if it's just for your private use) and the server will push out the message.
Though it'll probably be much easier to just have said App Engine server up and providing a WebSocket endpoint that your extension can connect to to receive commands in real-time, and some sort of API / control panel on the web (authenticated, of course).
Any free webserver-based solution would lag, as bad as 500ms, I think.
Try making a complementary native PC program: mobile apps for remote control usually have their PC part running as a background service or an application with just a shelltray icon. Such program opens a TCP/UDP port on PC and listens for commands from the mobile app, and can communicate with your extension via Chrome's native messaging API.
I have an Intranet http application running on several machines in our Windows domain; everything works when using IE 7 because I can configure it to use Kerberos authentication and I've figured out how to get one of the intermediate machines to be Trusted for Delegation.
I have researched and tried to get Firefox 3.0.10 to use Kerberos:
navigate to about:config
filter to network.negotiate
update network.negotiate-auth.delegation-uris and network.negotiate-auth.trusted-uris
with the following entries(separated by comma): http://jupiter2000/trimbrokerclient,http://johnxp/fileservicedemo
I have done this and even restarted Firefox and when I browse to the above sites on our LAN, I still get prompted for username and password and even when I supply them and the web page is loaded, I have some code in the app which displays the authentication method in effect and it is still NTLM, not Kerberos as when IE is used.
Can someone comment on how to get Firefox usable on this Intranet application of mine? Thank you.
p.s. while the names above are different, the app is the same. JUPITER2000 is IIS 6.0; JOHNXP is IIS 5.1.
From what I have done myself, you will only want to input the domain, and not the http:// or path.
There are 5 settings that need to be changed in FireFox.
Only the domain is necessary.
See them all here:
FireFox settings for Integrated Windows Authentication
you must use just the server name:
jupiter2000,johnxp
Whenever I try to access a NTLM authenticated intranet site, Safari takes forever to process and then comes back with "The sever is unavailable" or if allowed by the site, loads with out authenticating. I can access these same sites with no problems in both Firefox and Internet Explorer. The sites are hosted on IIS6 and are being generated with either ASP, ASP.Net 1.1 or ASP.Net 2.0.
Any insight on why Safari choking on these sites? Are there any work-arounds to get NTLM to correctly authenticate with Safari?
Update:
In further playing with it I have determined that NTLM will work (with the page loading reasonably fast) if I am using the FQDN for the site (i.e. http://mysite doesn't work, but http://mysite.domain.prv will work). Unfortunately, this will not work due to other constraints on the project.
Does anyone know why the FQDN would work but the shorter name will not? Is this something that can be worked around or is it "Sorry out of luck"?
Update 2:
According to the Wireshark packet sniffer, safari sends a SYN to the correct severs IP address. The intranet sever responds with a SYN, ACK, to which safari sends an ACK. This is the end in communication between safari and the sever. When attempting to access the intranet site by FQDN these three packets were the same but were then followed by a HTTP GET request, which then successfully loaded the page.
Because Safari is connecting to the correct IP address, I find it hard to believe that Safari just doesn't support NetBIOS/WINS names. Additionally, because the NTLM packets are never exchanged as safari never sends the initial GET request, I'm certain that NTLM has nothing to do with this issue.
Does anyone know the status of safari's support of NetBIOS/WINS?
In a similar situation with a Java based B2B client, I was successful in using http://ntlmaps.sourceforge.net/ to traverse the proxy.
Any insight on why Safari choking on these sites?
Because NTLM is not a web standard. You can't expect any given web browser to support it.
Until recently only IE supported it at all. And Firefox's support has to be specifically configured.
Firefox has always been able to traverse NTLM sites. I know because I'm stuck with this god awful custom ASP solution and SharePoint site to use in our intranet... Firefox is a dream.
Apple.. fix Safari kthx?