New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring HTTPS in ASP.NET Core 2.1 #110

Open
JuergenGutsch opened this Issue Nov 16, 2018 · 14 comments

Comments

Projects
None yet
3 participants
@JuergenGutsch
Copy link
Owner

JuergenGutsch commented Nov 16, 2018

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Digital Elvis on 09.07.2018 14:41:38

hacker, or just hack shill , 2.1 has been pulled, to buggy, FYI .net core is DOA

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Jürgen Gutsch on 10.07.2018 06:52:57

Maybe it is just hack shill, maybe just playing with words ;-)
> "Why ASP.NET Hacker? It doesn't really have a deeper sense. I chose this name because we got some blue ASP.NET Hacker badges on the ASP.NET hackathon at the MVP Summit 2015 in Redmond. I think this matches exactly what we do with ASP.NET, if we want do achieve the customers requirements." (https://asp.net-hacker.rock...

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Neutrino . on 04.08.2018 13:45:23

Dotnet Core DOA, lol. What kind of retarded alternate reality are you living in? Here in the real world Dotnet Core is supporting enterprise solution development all over the world.

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Digital Elvis on 04.08.2018 17:40:23

the full farmework FUD from HanselMupppet have poisioned ASP.Net
https://uploads.disquscdn.c...

don't even try saying the 2 is for core 2.0 , I been motioning it for years, core has way way less than < 1% aka DOA

But almost everyone's (pros, not bloggers of course) given up hope on Core every amounting to anything
https://uploads.disquscdn.c...

version 1 got more downloads then every other version combined and just look at the total indifference to the latest versions, we're talking funeral, dead, buried.

just look at the compatibility pack Kevin Gallo was touting only a few months ago.

https://uploads.disquscdn.c...

that's what effectively zero interest looks like, if the level of interest in core was the level of polonium 238 in drinking water it would be safe to drink.

it's main support is from Blogger/MVP wanna beez and F@nboyz, period.

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Neutrino . on 07.08.2018 13:57:54

What's any of that supposed to mean? ASP.Net ran to version 5 and has since been superceeded by ASP.Net Core (which is ASP.Net 6) which is modular, open source and cross platform. What's not to like?

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by abs on 30.08.2018 08:10:20

Thanks for the guide Jürgen. I have a question if you don't mind. How would I go about allowing other hosts to connect? The reason that I ask is that I'm trying to host this on a Linux server and connect to it from my Windows machine.

For a .net core 2.0 http website I've got it to work by adding .UseUrls("http://0.0.0.0:5000") to the BuildWebHost() method in Program.cs. I've tried using .UseUrls("https://0.0.0.0:5001") but get the following error:
Unable to start Kestrel.
System.Net.Sockets.SocketException (13): Permission denied

I've tried searching for this error message to no avail.

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by abs on 30.08.2018 23:51:02

Figured out the reason. There were typos in the Program.cs and I may have been running the web application already in a different session which probably didn't help.

This is what I should have added:
.UseUrls("http://*:5000;https://*:5001");

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Nov 16, 2018

Comment written by Balaji hope tutors on 15.11.2018 14:39:46

Thanks for the guidance, i am hoping for the quick light on the Dot Net Course

This comment has been minimized.

Copy link

CoolOppo commented Nov 23, 2018 — with utterances

How would I go about using user secrets to pass the password to listenOptions.UseHttps(...)? I can't fetch the configuration from within Program.cs no matter what I try. I've been Googling solutions for like a half hour so any help would be greatly appreciated.

@lazywinadmin lazywinadmin referenced this issue Dec 2, 2018

Open

New comment system #8

1 of 3 tasks complete
@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Jan 28, 2019

Hi @CoolOppo
I'm currrently working on a blog post about this. Will publish it tomorrow or on Wednesday

This comment has been minimized.

Copy link

nabokov-ef commented Feb 12, 2019 — with utterances

Typos:
Strinct
dotnet dev-certs https --trust

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Feb 13, 2019

@nabokov-ef many thanks for your comment.
I don't really get, what you try to tell.

@nabokov-ef

This comment has been minimized.

Copy link

nabokov-ef commented Feb 13, 2019

@JuergenGutsch

This comment has been minimized.

Copy link
Owner Author

JuergenGutsch commented Feb 14, 2019

@nabokov-ef great thanks :-) I thought about that but didn't find the typos yesterday.
I just fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment