SSL KB article query

[rbjtech 5284]

Assuming this is Windows ? - Just disable and re-enable it in the Windows GUI.  Or you can use Netsh via Admin command line.   

 

[MBSki 1114]

1 minute ago, rbjtech said:

Assuming this is Windows ? - Just disable and re-enable it in the Windows GUI.  Or you can use Netsh via Admin command line.   

 

got it, thanks. I'll give it a shot. 

Edit: Yes, windows. 

Edited June 16, 2023 by MBSki

[Painkiller88 249]

by adding a cert is not possible to shut down or disable a physical network port.

referring to the OSI layer model this should be a clear thing:



so whatever happened must be something else. do you have a static local ip?
have you assigned the domain to your public ip?

are you opening your server by ip or domainname?

[MBSki 1114]

1 hour ago, Painkiller8818 said:

by adding a cert is not possible to shut down or disable a physical network port.

referring to the OSI layer model this should be a clear thing:



so whatever happened must be something else. do you have a static local ip?
have you assigned the domain to your public ip?

are you opening your server by ip or domainname?

Yes I have a static local IP. I believe I assigned the domain to the public IP because I can access my server with only the domain name.

And I think I opened the server by both io and domain name 

[Painkiller88 249]

5 hours ago, MBSki said:

Yes I have a static local IP. I believe I assigned the domain to the public IP because I can access my server with only the domain name.

And I think I opened the server by both io and domain name 

ok, so what i do, internally i only access the server by local ip because of the following reason: there is no need for me to route the traffic externally if it is just for my local use.

another thing you can do, if you really want to access your server by domain (if your router allows this) because not every router is able to do local loopback.

in windows make a host entry so yourdomain.com points to the local ip of your emby server, this is not the prettiest way but a very quick to make sure your local pc will always use the local route. 

And also check you don't have a mess with port forwarding so maybe this is the reason you can't access your server anymore from the inside.
 

[MBSki 1114]

5 hours ago, Painkiller8818 said:

In windows make a host entry so yourdomain.com points to the local ip of your emby server, this is not the prettiest way but a very quick to make sure your local pc will always use the local route. 

And also check you don't have a mess with port forwarding so maybe this is the reason you can't access your server anymore from the inside.

Ah, I didn't make a host entry. I'll have to try that. Do you think a lack of a host entry could've shut down the port?

I didn't change any port forwarding so that can't be the issue.

[Painkiller88 249]

3 hours ago, MBSki said:

Ah, I didn't make a host entry. I'll have to try that. Do you think a lack of a host entry could've shut down the port?

I didn't change any port forwarding so that can't be the issue.

no, this is absolutely impossible. no software failure will shut down a physical port in your windows machine

[MBSki 1114]

7 minutes ago, Painkiller8818 said:

no, this is absolutely impossible. no software failure will shut down a physical port in your windows machine

So you think my hardware just failed coincidentally at the same time I was trying to setup my cert?

[Painkiller88 249]

3 hours ago, MBSki said:

So you think my hardware just failed coincidentally at the same time I was trying to setup my cert?

yes something like this.

your network adapter don't bother if you have ssl or not.

[MBSki 1114]

1 hour ago, Painkiller8818 said:

yes something like this.

your network adapter don't bother if you have ssl or not.

Ok, I'll do some more testing next week to confirm.

[MBSki 1114]

Took me awhile but I finally got to retest my original network port that seemed to fail. Interestingly, it came back to life after I refreshed it in Windows. That's not to say there isn't still a hardware issue with it, as I haven't left it on very long, but it is interesting that it came back at all.