Visual Studio Iis Express Your Connection Is Not Private

0 views
Skip to first unread message
Message has been deleted

Bubba Lual

unread,
Jul 12, 2024, 7:24:20 PM7/12/24
to igenigoub

When clicking on some URLs of web sites I've been using for ages, this past week Chrome keeps telling me "Your connection is not private" (See attachment). I'm using a MacBook, Os 10.11.6. Some of the sites this happens on have always worked with no problem, and some are well known sites in my part of the world. Is this to do with some annoying new 'feature' that they've added in Chrome? And before you start on about Safari, it does the same anyway, but I prefer Chrome as a browser. Who do they think they are to tell me I can't visit a perfectly reliable site? There's no way I can get over this, having searched the settings in Chrome, and it's really annoying me.

I can Confirm a fix that worked on both a 10.9.5 & 10.11.6 Mac OS users. Simply set the DST Root CA X3 to "Always Trust" on several Mac's I manage in an office and home's this fix work for 4 websites that previously had issues with this CERT ERR.

visual studio iis express your connection is not private


Descargar Zip ---> https://urluss.com/2yOtmi



User wrote " I really do tire of this relentless push to update " well, as Technology Changes and Certificates Expire - one may move forwards or get left behind, as Bob Dylan has been quoted " The Times that are a changing "

The Age of this computer will Govern what newer version of macOS it will Qualify to install. Use About this Mac from the Apple Icon on Desktop - the required Information will be there.

With the above information in-hand - follow this How to get old versions of macOS and verify what version this computer Qualifies to install. For Best results use Safari to commence the download as Others may not work.

Are there any AntiVirus, Disk Cleaner, Optimizers, Un-installers, etc installed which should be removed as per Developers Instructions. They are useless, unneeded, cause havoc and interfere with the normal operation of the OS and may even Corrupt the OS requiring a Reinstallation

Thanks etresoft for taking the time to respond. Regrettably, this is not a complete answer. I developed this problem with Safari some months ago so moved to Chrome and the problem went away. Yesterday it appeared with Chrome and Firefox and Safari on a safe local company's web page and many others. The page opens fine on the company management computers and also my iPhone, iPad and a Surface Pro. In addition many other sites do not load properly now, I get boxes with question marks and functions won't work. I could not log onto watch a MotoGP video on my Macbook, but both my phone and original iPad Pro loged on fine using keychain.

Everything worked ok two days ago and not yesterday or today. So something changed over night. It is a bit glib to simply say that I need a new laptop cos mine is old. Possibly I do at some point soon. First, without a root cause for the problem I will not be buying another Mac. Secondly, my Macbook Pro did not suddenly age over night. Something has changed somewhere.

My problem is that the site works fine on three other devices I own and on the CEO and IT Dept computers. Also these sites all worked last week. So something changed over night. The question which YvonneMarie and I have is what changed and how do I change it back?

This is not a new issue. I have read solutions lists in google search results and tried them all including deleting and reinstalling Chrome. A pain as stored details are lost. All to no avail. This is an long standing Apple problem. Help please Apple. Help or I am a casualty to your brand.

Older versions of macOS have certificates that may have expired. If Safari doesn't work, you'll have to use Chrome. If Chrome doesn't work, you'll have to use Firefox. If Firefox doesn't work, you'll probably have to get a new computer.

My Mac runs El Capitan, but that wasn't an option in the list I was given, which is why I didn't select it!! I really do tire of this relentless push to update. Some of us are retired and we can't just fork out a cool grand or more to replace our laptops.

etresoft Brilliant, thanks. At last a root cause. Thanks also P. Phillips . I have some spare time this coming week and will look to update to a newer version of OS. I tried Catalina many months ago and had major issues. Possibly jumping multiple versions in one go. Possibly the 64 bit issue. Then OS roll back also failed and I had to pay a wad of cash to a support firm to rebuild my laptop. Being gun shy, I went back to what worked, El Capitan. My observation from others is that Catalina does not work well with old machines so possibly better to go to Sierra or Majove? This time I will roll forward one at a time and get to a supported system.

And thanks for the advice etresoft I will get a new machine. I would really like an Apple with a touch screen and full OS. iOS does not cut it for a serious work from home desktop setup. I work paperless so write-on-screen is essential for meetings and meeting preparation. The iPad certainly has the best write-on-screen experience, but as I said iOS simply does not cut it, so Apple means two devices! Maybe, gulp, the new MS Surface Pro 8 is the answer......

Posting in Big Sur and as per user profile " MacBook, OS X 10.11" El Capitan can this be clarified what version is under discussion Big Sur or El Capitan being used on the problematic computer.

Your connection is not private
Attackers might be trying to steal your information from www.community.brave.comcom (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_DATE_INVALID

community.brave.com normally uses encryption to protect your information. When Brave tried to connect to community.brave.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be community.brave.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Brave stopped the connection before any data was exchanged.

I followed the instructions in this video, and it seems to have solved the problem. It was only an hour ago, so I consider this a preliminary report. I will let you know if I encounter any further problems.

I have read on another question, that visual studio accepts rsa keys only in PEM format, so I generated the key in that format using ssh-keygen -m PEM -t rsa -b 4096. I have tried with, and without pem format all kinds of different key sizes (1024, 2048, 4096, 8192) with and without passphrases. I have tested each one of those keys by adding the public key to my authorized keys file on my ubuntu laptop and connection from WSL2 using the generated key (ssh -i user@host). It worked every time.

I have also read on this question that you should generate the key using puttygen and then exporting the openssh key. I tried that also, with and without passphrases, though only with the default key size. Again connecting from the bash terminal from WSL2 works fine using those keys, but I can't connect in MSVS.

The error messages from visual studio's connection manager make no sense either. When I click connect, it asks me to confirm the fingerprint of the host, and to add it to the known hosts file. When I click yes, the input fields for the connection manager turn red. Hovering over the red fields yiels the results:

I'm not quite sure what that means. My host has an rsa key file formats in their home/.ssh directory. Visual studio says when first connecting that the key fingerprint is "ecdsa-sha2-nistp256", which is supported according to the documentation.

If using ssh-keygen to create the private key, you must specify the switch -m pem, or the key will not be accepted by Visual Studio. If your private key begins with -----BEGIN OPENSSH PRIVATE KEY-----, you must convert it with ssh-keygen -p -f -m pem.

Some web browsers, like Google Chrome, will push an Update notification to the right of the address bar. Initially, the notification will be green, then it turns to yellow, and then red. Hit the Update button as soon as it appears.

You can also add a layer of protection on public Wi-Fi using a virtual private network (VPN). A VPN encrypts your data, hides your IP address, and routes your internet traffic through a different server in another location. This makes it more difficult for third parties to track or intercept your connection.

Sometimes, the error might be caused by a temporary glitch, like a problem with your internet connection or your system not using the correct date and time. However, it is always best to be cautious and avoid entering personal information on a website displaying the error.

Hey everyone,I have been suffering a hard time connecting to my EC2 instance with SSH recently. At the beginning I could connect to it but for somehow reason I lost my connection. (tried both with my VS code studio and terminal) Here are what I have been tried to troubleshoot the problem:

The fact that you can SSH to the instance's public IP when it is first started shows that your security groups and routing tables etc. are likely all correct. but then a short while later (are we talking hours or days?) you can no longer connect.

Does the security group allow ingress on TCP port 22 from any address (0.0.0.0/0) or did you select "My IP" when setting up the security group for the instance? If it was limited to your IP then has that changed - depending on your ISP your Home IP address can change periodically, and obviously your IP is different at home/at work/on VPN/on cellular.

The other thing I'm thinking of is that to be running within free tier you must be using a t2.micro or t3.micro instance, which are pretty puny. What else are you running on it? You may be running something that is fine at the start, but slowly consumes more and more resources until you can't login any more (it will still show up as running and 2/2 checks passed in AWS Console as it's still actually running, though unusable). Select the instance in AWS Console and look in the Monitoring tab, is there anything of concern in here?

d3342ee215
Reply all
Reply to author
Forward
0 new messages