I am setting up EAP-TLS authentication using the manual https://networklessons.com/wireless/peap-and-eap-tls-on-server-2008-and-cisco-wlc/.
My server and client details are below:
Server: NPS 2008
Client: Linux
I generated the server certificates on the NPS server as well as the CA cert. I imported the CA cert to the Linux server but after this the manual I am using tells me to log into the IP of server using a web browser and request client certificate from there.This is the part I am stuck in.
I tried curl -k https://< ip of server > but this returned an error:
curl:(7) couldn't connect to host error.
Any help will be appreciated.
Have you checked:
httpd is running on the server
httpd is listening for TCP on port 443 (I like ProcessMonitor from MS for this)
https://localhost/ access from the NPS server (to itself) works as expected
firewall on the server is shut down or is allowing https access on the correct
network interface
https://ip_address/ access from the NPS server (to
itself) works as expected
https access works from another client on
the same LAN segment
Related
I want to run code on a server(a system with high configuration and GPU). Now, I have got access to the server through VPN. I am using a VPN client and entered the credentials. The VPN client says "connected". how do I get access to the terminal of the server?
I have a software running on my server which is called Gitlab. The service is accessible through a SSH, HTTP and a HTTPS endpoint. All three access points are reachable through a SSH tunnel, so binded to 127.0.0.1.
> 127.0.0.1:80 # HTTP
> 127.0.0.1:443 # HTTPS
> 127.0.0.1:1234 # SSH
To enable HTTPS, I created my own SSL certificate but of course there is no authority which confirms its authenticity. So even if I satisfy my server to work with it, I am wondering if I should even continue using it.
There are a lot of services on the server, or client tools which connect to it, and all would need to respect their system keychain where the public key is stored in as "trustworthy". Does anyone have experience with this constellation?
Using a self-signed certificate is the default configuration, to speed up the startup process, and it's up to you to decide if you want to install a trusted certificate from a third party CA, or a local CA (maybe your AD integrated CA). If a service is local or internal to your company, you can decide to keep it self-signed.
In the environments i was involved with, there was a AD integrated CA and we signed everything with that.
Further informations: https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/ssl_tls_concepts.html
Ι have an IoT device posting data to a web app hosted to IIS 6.2.
Posting with http is working perfectly. When i change it to https i am getting handshake error.
The same web app has web interface that uses the same SSL certificate and works perfectly on all browsers. Thus I guess, that SSL setup is correct.
I have tried to change the server certificate with a self signed certificate create from IIS with the same results.
I have also tested the IoT device to other servers with SSL and it works.
Here is the wireshark communication
and here are the SSL protocols available on server
i am also attaching a report from ssllabs
any ideas?
I want to use https (port 443) for my web app which is developed using NodeJS express mongodb.In order to do that I know I need to get ssl certificate. My app is hosted by Amazon ec2. My express server listens port 3000.I created ssl certificate using Amazon Certificate manager ,and I also set up apache following some tutorial. However when I go to port 40 I see apaches page (I used to see my app here since I redirected port 80 to 3000 before). When I do https request it just gives me nothing.I set load balancer and attached to my ec2 instance.Is there a good tutorial or can you tell me what I am missing? This became so annoying.
In Azure, I set up the Windows Server 2012 R2 FTP service properly and have no problems connecting via the standard Windows 7 FTP client when the server-side setting is "Allow SSL". My endpoints are properly defined, etc.
However, when I change the setting to "Require SSL", I am unable to connect. I set endpoints for FTP SSL ports 989 and 990. I have a certificate installed properly (bound to HTTPS port 443). I selected the same certificate for use with FTP.
Note: When the server is set as "Allow SSL", Filezilla connects using TLS successfully. Neither FileZilla nor the Windows 7 FTP client can connect when the server is set as "Require SSL".
I want to require SSL connections when using the Windows 7 FTP client. I do not care about FileZilla (that was just for testing). I cannot find any walk-throughs or examples where the author uses the "Require SSL" setting on an Azure machine.
Suggestions to fix?