l3gion

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

2 Neutral

About l3gion

  • Rank
    Newbie

Converted

  • Location
    Germany

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. PIA needs to get their stuff in order, thanks will try that fix Best.
  2. Hi, What do you mean by "your actual PIA user name"? I'm using my PIA user name already. I Reverted to my previous container version using a backup and it's working again. Best.
  3. Hi all, I'm also unable to get connected to PIA servers anymore. I keep getting this warning: 2020-11-07 16:21:21,750 DEBG 'start-script' stdout output: 2020-11-07 16:21:21 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. I tried several OVPN config files from PIA, with different ciphers and none is
  4. Ok, today had some time to clean the server, was a bit dusty inside. It's beep up now for 5 hours and it's still holding at 1gb speed.
  5. Thanks for the suggestion, but I'm not that is the cause, as a reference my cpu sits around 35-40ºc and the array drives 25-28ºc, so temperature is pretty low in general inside the case.
  6. I'm looking into it. Different cable and diffent hub port have the same result. I'll try to get an add in network NIC to see if the problem goes away. Thanks guys.
  7. HI, My server is randomly drops my network speed from 1gb to 100Mb, today I caught it on the log: "vnstatd[6095]: Detected bandwidth limit for "eth0" changed from 1000 Mbit to 100 Mbit." My network is the Motherboard integrated one, from a Fujitsu D3417-B2 I also didn't used to have this drops in speed, I think they only started since upgrading to 6.8.0 If I restart the server the speed is back to 1gb, but having to restart every couple of days would be pretty annoying.... Anyone else has this issue too? Any idea what it could be?
  8. Also updated from 6.8.0 here, all up and running here
  9. Hi, Can't seem to get the path to work, I'm using a path in /mnt, but it still errors: I also tried to disable restrictive validation, but the same occurs. Best.
  10. I have the same error after updating too.
  11. Not automatically, I have to run "./manage.py document_consumer" in the docker console. But I don't know why or how to run it at start automatically.
  12. No problem :) did you get the consume process to run automatically?
  13. Hi, Just run ./manage.py createsuperuser in the docker console.