Hey how’s everybody doin’?
NIC stands for Network Interface Card. 
I’m not sure you were successful, as I can see IPv6 in your After Reboot log.
Oct 12, 2019 13:32:51.511 [11620] INFO - Plex Media Server v1.18.0.1913-e5cc93306 - Microsoft PC x64 - build: windows-x86 windows - GMT 02:00
Oct 12, 2019 13:32:51.511 [11620] INFO - Windows version: 10.0 (Build 18362), language fr-FR
Oct 12, 2019 13:32:51.512 [11620] INFO - 4 3392 MHz processor(s): Architecture=0, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
...
Oct 12, 2019 13:32:52.219 [11596] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
...
Oct 12, 2019 13:32:54.023 [11696] ERROR - Error issuing curl_easy_perform(handle): 7
Oct 12, 2019 13:32:54.023 [11696] WARN - HTTP error requesting GET http://127.0.0.1:49816/system/agents (0, No error) (Failed to connect to 127.0.0.1 port 49816: Address not available)
Oct 12, 2019 13:32:54.023 [11696] DEBUG - [com.plexapp.system] HTTP reply status -7, with 0 bytes of content.
Oct 12, 2019 13:32:54.023 [11696] WARN - [com.plexapp.system] Couldn't connect to plug-in, treating as dead.
Oct 12, 2019 13:32:54.023 [11696] DEBUG - Stopping [com.plexapp.system].
Oct 12, 2019 13:32:54.023 [11696] DEBUG - [com.plexapp.system] Killing.
Oct 12, 2019 13:32:54.024 [11696] ERROR - Error parsing content.
Oct 12, 2019 13:32:54.024 [11696] ERROR - Exception caught while updating system agent list: Error parsing file
When an exception is caught, some plex process crashed. That’s not normal. It generally does not also complain about the 127.0.0.1 address being unavailable.
Here it lists the Network Interfaces it knows about, and the IP addresses.
Oct 12, 2019 13:32:54.034 [12108] DEBUG - Spawned plug-in com.plexapp.agents.lastfm with PID 12172
Oct 12, 2019 13:32:54.034 [12108] DEBUG - [com.plexapp.agents.lastfm] Sending command: GET /:/prefixes
Oct 12, 2019 13:32:54.038 [11596] DEBUG - NetworkInterface: ignoring adapter 'Ethernet 2' (fe80::fd4d:ba2:18bc:8a2f%3,169.254.138.47) because it has no gateway
Oct 12, 2019 13:32:54.038 [11596] DEBUG - NetworkInterface: ignoring adapter 'Loopback Pseudo-Interface 1' (::1,127.0.0.1) because it has no gateway
Oct 12, 2019 13:32:54.038 [11596] DEBUG - Detected primary interface: 192.168.1.13
Oct 12, 2019 13:32:54.038 [11596] DEBUG - Network interfaces:
Oct 12, 2019 13:32:54.038 [11596] DEBUG - * 9 Ethernet {5B744706-ECDA-400D-8F67-D5E116D59B55} (192.168.1.13) (loopback: 0)
It was showing an IPv6 address, but it didn’t show 127.0.0.1 as an additional loopback connection.
Your logs also show a variety of odd problems: database is locked, unknown metadata type, curl error 3 (malformed url), curl 28 timeouts. The goal is not to have those, but I can’t say why you have them. I myself have the database is locked error right now.
I’d suggest a few things:
- disable IPv6 more
- uninstall any VPN you have
- reboot the computer if you did
- run MS System File Checker
- reboot the computer if sfc does anything
- test PMS and get a log.
If you can’t get to the screens shown below, let us know and we’ll find a way to do it in a text file.
