Error while initial run

[ccw2777]

When attempting to run intelowl for the first time it appears to hang on "Task intel_owl.tasks.check_stuck_analysis[be17545d-a109-4001-8dc7-cb08e9626979] succeeded in 0.0158641804s: None"

I am also seeing the message "requests.exceptions.ConnectionError: ('Connection aborted.' ConnectionResetError(104 connection reset by peer)".

Can this be troubleshot further and fixed, or is there a way to purge intelowl and re-install/rerun everything? Thank you!!

• The "./initialize.sh" was already run successfully prior.

[mlodic]

show docker ps command and provide more details please

I don't even understand whether this is a problem or not from the info you provided. Also, please check out all the documentation and other issues before opening a new one.

[ccw2777]

Working on providing more details

[ccw2777]

What happened,
So I followed the intelOwl config guide to do a fresh installation of IntelOwl. I followed every step including altered the files env_file_app and env_file_postgres, and I've double-checked that the credentials are exactly the same.
When trying to deploy it hangs for a while at the below screenshotted area (INI configuration) and then after 5-10 minutes it goes to the previously screenshotted intel_owl.tasks.check_stuck_analysis line and hangs there.

Environment
OS: Ubuntu
IntelOwl version: newest

How to reproduce your issue
Fresh install of IntelOwl on Ubuntu, follow the install steps on docs

Error messages and logs
Could use help on being told what logs I should be providing.
Thank you very much for any help!

at the end of the day if this fails to be resolved is there a way to fully uninstall/cleanup and do a fresh pull request and install?

[ccw2777]

It will also hang at the reoccurring line "Connection reset by peer" as previously mentioned.

[ccw2777]

Completed a complete rebuild and it hangs at "getting INI configuration from /etc/uwsgi/sites/intel_owl.ini" for a while before moving forward and hanging at the above screenshot again.

Possible causes. Running python version 3.1 with 3.9 also installed,

UNABLE to locate the folder "uwsgi". Attempting to find the path etc/uwsgi/sites/" found nothing created at this point.

[ccw2777]

What creates the file "intel_owl.ini"? Its nowhere within the host after trying to install intelowl

[mlodic]

that's the application server (uwsgi) configuration.

Have you tried to use the application from the GUI? Did you face any error there?

Then, you should extract the errors from the log files in the paths stated by the doc: https://intelowl.readthedocs.io/en/latest/Contribute.html#debug-application-problems

Anyway, I am not sure even if there is actually a problem here. Please do more efforts and try to use the application... only then provide feedback there. ty

[0ssigeno]

Working on providing more details

From this it seems like the cronjob of Tor is your issue: in the specific, it is unable to retrieve information from https://check.torproject.org/exit-addresses. On the why you have this kind of issue, unfortunately i'm unable to reproduce on my side: can you try to inside a celery container e manually try to retrieve the information from this url? I think it is something related to your network in particular

[ccw2777]

I was able to get it to work successfully. However, after upgrading to version 5 I am running into the exact same hangup (shown below) where Intelowl stays indefinitely. I didnt see any previous issue posting regarding this problem. This is the ONLY thing keeping it from running, and I am not finding much info on what part of IntelOwl could be causing this. Any suggestions would be greatly appreciated!

Intelowl_celery_worker_default | requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')).

[0ssigeno]

Mmmmmh, we did not change anything related to the communication between containers, and i'm unable to reproduce on my side.
Do you have any custom routing going on in your machine? Any other container up at the same time as intelowl? Vpns?

[taylor-madeak]

I got looped into this because I'm one of @ccw2777's colleagues. It appears that our firewall may be the issue.

While connected to VPN:

openssl s_client -connect check.torproject.org:443
CONNECTED(00000003)
write:errno=0
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 312 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Disconnected from VPN:

openssl s_client -connect check.torproject.org:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = check.torproject.org
verify return:1
---
Certificate chain
 0 s:CN = check.torproject.org
   i:C = US, O = Let's Encrypt, CN = R3
 1 s:C = US, O = Let's Encrypt, CN = R3
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
 2 s:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   i:O = Digital Signature Trust Co., CN = DST Root CA X3
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIGLjCCBRagAwIBAgISBMNMu+EbifyMbYz0QUY+amKvMA0GCSqGSIb3DQEBCwUA
MDIxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQD
EwJSMzAeFw0yMzA1MTcwMDE3NTRaFw0yMzA4MTUwMDE3NTNaMB8xHTAbBgNVBAMT
FGNoZWNrLnRvcnByb2plY3Qub3JnMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEA/DVnKJkMzIa8ExOQhMAkRemjY71ghZN0KVoZm/oHfHUSq9Jg+zjvZbTV
rSNkmIVZ1+3c99bMkRZBKMqtxDVHbfdrhtwx6L2LgCWZoD4PoBTCvzJYDIMlDN3E
dQ+kPEQr0I6hGorG+Vd9I6Xp54ikuwLH6JFA/7UOuGUnqv8bVt7titWwGm96L9Iw
wbZki7SmPOsnYqLzkLZ4TIFBFUW9bKLjWxoRwrPHar6WCeLXxwcMKWJHQNcWH7Hs
QhK9aKO4j2e1dJ6zJ675tNFHBeppa1nHKHOfbVsHWzoRyzq35LOHuS3KEQ2swmIK
tsgu2YiIVnNbcny1tIwviu9BS0OyXMUtdXJJVTyOZuA+eld9EEmhJO0bm3mU8uuV
hmm+mWSY5C4HW86XwLhah6FcdhaHc7aU4Uha7gJam0AjgHB0DgcUx1ty5Oqhz0Sq
bAMMmgKLTjbLe9Lx0FWl9mZMVQOEz/8NHY5cMnRcMuERWmhwi5zfW7aneYsNMvpe
naMbVVeAvAC6sbibNjnw4UMbqaD5Go96tGYuYLtrel4n/vgAA0kz/fyWHME9tghL
tFxw5ccPx8X30pVokAaPqpj7lKVPyz/i2VF2mDQoD4UNZ8GtVRLkgtO4rkn+Zf7H
blr1SESXyY30J9iSK2VLKoyQ0s8WnVyNud8hh9Wpr33l3i36aGcCAwEAAaOCAk8w
ggJLMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUH
AwIwDAYDVR0TAQH/BAIwADAdBgNVHQ4EFgQUCAUDkOOOPQlAZ32dqyDSxM5yOE8w
HwYDVR0jBBgwFoAUFC6zF7dYVsuuUAlA5h+vnYsUwsYwVQYIKwYBBQUHAQEESTBH
MCEGCCsGAQUFBzABhhVodHRwOi8vcjMuby5sZW5jci5vcmcwIgYIKwYBBQUHMAKG
Fmh0dHA6Ly9yMy5pLmxlbmNyLm9yZy8wHwYDVR0RBBgwFoIUY2hlY2sudG9ycHJv
amVjdC5vcmcwTAYDVR0gBEUwQzAIBgZngQwBAgEwNwYLKwYBBAGC3xMBAQEwKDAm
BggrBgEFBQcCARYaaHR0cDovL2Nwcy5sZXRzZW5jcnlwdC5vcmcwggEEBgorBgEE
AdZ5AgQCBIH1BIHyAPAAdgC3Pvsk35xNunXyOcW6WPRsXfxCz3qfNcSeHQmBJe20
mQAAAYgnSP4oAAAEAwBHMEUCIQC3bAWZI8tDThJZMLJySWdyiMIPeXa6RoTJWhds
2b9KeAIgPJY26tKOs+0DHYxEnz/oI+c5liHwLYlh4eNTroj6FjQAdgDoPtDaPvUG
NTLnVyi8iWvJA9PL0RFr7Otp4Xd9bQa9bgAAAYgnSP4oAAAEAwBHMEUCIQDychaX
jicLBzgJjl6zulHPfGeOFoSJuqd6gUsiUtCjTQIgbtq3V74dh5o8PkuvGzSvdwho
zR2yGvqhuSuF0bqK8lYwDQYJKoZIhvcNAQELBQADggEBAEqs8SzTRrh+K2E32c7b
5wXNC/qnRWjfMe7R680Yg8m9lma8ZTdww5RZXlYbmD5rFDebxFNxGGSMznCP6/ml
MhSP1xjpkzCJ/fvZ2WLi+9parJItgz7RyiHrzKgelktazOJaUG+z1Fn5NBgyM+1Y
W8P/F+o40xCCa1dYdPrUie+9fmvDugOfUnMqKUjnQXy/buJnC5yUWR2ByIUivZJJ
qIvrHbWp60UlTCjfwC/+zn5Jsvv47myRHzeC9a+kA+zszwVlqYSLJXuESuHL6/Sy
gYLX7xbcvO7oO6lE3AeAuLZ3aJAxomkhjfhwHJJLiEIVkrIhu/kIN9iGqAH8S9xI
Dlg=
-----END CERTIFICATE-----
subject=CN = check.torproject.org

issuer=C = US, O = Let's Encrypt, CN = R3

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 5098 bytes and written 392 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: CCC02667CBE5EFC2D17991AB8EA9D5378686090A65E3C5B4FE9B13E4D90DAAB3
    Session-ID-ctx:
    Resumption PSK: 287752AC7ED57864EB082A54C7547391BD74C50FA9086B0F49827AEE26DD26575F19F61FD12A83018A4AF84EF72BFD28
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 40 e2 11 49 08 57 59 0e-57 bb 85 d9 b3 e1 fe 87   @..I.WY.W.......
    0010 - f4 24 bd 1c 1d 6d 25 8c-91 52 0a a7 12 55 4b f7   .$...m%..R...UK.
    0020 - a8 a7 45 80 1c ad 6c 34-7d b7 b3 c0 73 53 4d e5   ..E...l4}...sSM.
    0030 - 9d c8 2d a1 4d fa e6 6a-b0 61 41 c4 06 a4 8d 18   ..-.M..j.aA.....
    0040 - 3e e7 6c 5f 23 fe 0b 2b-70 20 52 03 72 ff 11 a0   >.l_#..+p R.r...
    0050 - 72 bd e3 c0 b9 78 33 20-a3 73 96 bd c5 8c 68 ac   r....x3 .s....h.
    0060 - 84 41 8a ac 03 84 3c c0-e0 dd cc b8 03 fd 27 86   .A....<.......'.
    0070 - 81 68 ec c0 78 00 96 3e-18 9b e2 4c ce d1 b7 2d   .h..x..>...L...-
    0080 - 9b 0f 65 f0 4f 80 7c b8-c1 42 27 f6 37 ce a7 d6   ..e.O.|..B'.7...
    0090 - 90 1e 66 42 9e e5 35 51-22 31 44 79 5d 4f 36 03   ..fB..5Q"1Dy]O6.
    00a0 - 23 12 d3 9f 73 88 25 6d-cc af 4d f8 9f cb 7d cd   #...s.%m..M...}.
    00b0 - 32 e4 6f a9 53 10 ba fd-d2 fd 88 74 23 eb 52 f0   2.o.S......t#.R.
    00c0 - a9 1c 96 66 04 25 8c 90-df 70 b5 47 55 4f 6f 36   ...f.%...p.GUOo6
    00d0 - 2f 23 a3 b8 06 ae ac 4f-bf 1e ff 99 b7 c0 95 91   /#.....O........
    00e0 - ca 85 14 68 1d 9e 0c d4-7a 32 81 c4 3e 5b 7c 0f   ...h....z2..>[|.
    00f0 - f3 ba 95 54 27 fd 63 6f-f0 1b 6f 9f 69 18 f8 c3   ...T'.co..o.i...

    Start Time: 1685647233
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 074C46E92DB39C86792867B1093C91EA344B0649EBF663524546483DF0C8EEFA
    Session-ID-ctx:
    Resumption PSK: 09419309FA81F2B74E3A1515121EFC065699A47CEF4CB532708EBE47C3C5C1977B053AECC7538449D4CBF87E9362D36C
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 40 e2 11 49 08 57 59 0e-57 bb 85 d9 b3 e1 fe 87   @..I.WY.W.......
    0010 - 9d db ed ac ff a2 4c 72-08 0c 31 22 a6 32 f9 60   ......Lr..1".2.`
    0020 - 45 7c a6 cc 7e d7 8e 02-8e 62 bb 42 72 b7 da 9f   E|..~....b.Br...
    0030 - 54 0c 55 b9 d9 30 27 57-81 bc bd 4d eb f3 e4 07   T.U..0'W...M....
    0040 - 52 85 33 49 16 7e 42 2a-b2 6d d2 5d 56 63 d3 8f   R.3I.~B*.m.]Vc..
    0050 - 6b c2 f1 9a 0a 8b 51 b5-4d 3a 6d b3 c6 2f f8 77   k.....Q.M:m../.w
    0060 - d7 77 c9 26 ed fe 99 0b-30 10 b6 e4 ce ab f1 f6   .w.&....0.......
    0070 - 76 bc f2 3e a7 32 fc c4-55 8a 45 6c 3f 0e 4a 8d   v..>.2..U.El?.J.
    0080 - 6c 7d 62 4e 48 1c 71 97-7a f7 08 34 01 a9 4f 24   l}bNH.q.z..4..O$
    0090 - 8c 82 26 df ba f8 87 1b-b7 a5 b8 7c 15 08 0a 79   ..&........|...y
    00a0 - 0c 1d 46 40 ab d6 45 0c-53 f2 21 06 42 6c 7b 0f   ..F@..E.S.!.Bl{.
    00b0 - 9a 4e 33 08 f1 3b 11 2f-8b 80 bf db d6 4d e4 0d   .N3..;./.....M..
    00c0 - b8 5e 89 94 5c 21 aa af-7a ee aa 22 b1 c7 28 01   .^..\!..z.."..(.
    00d0 - b7 37 e6 58 76 b7 a5 20-52 6b ca d0 7a 1e a0 57   .7.Xv.. Rk..z..W
    00e0 - 9c 3a fc f6 69 48 15 7d-92 82 3f 03 64 f5 9b f8   .:..iH.}..?.d...
    00f0 - 1b c5 6b f4 b4 08 7e f1-d1 40 64 82 50 ad cc cb   ..k...~..@d.P...

    Start Time: 1685647233
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
closed

[ccw2777]

@0ssigeno @mlodic is there a way to get IntelOwl to skip Tor for the time being so that it no longer hangs when trying to access check.torproject.org.

[mlodic]

Have you tried to use the application from the GUI? Did you face any error there?

Then, you should extract the errors from the log files in the paths stated by the doc: https://intelowl.readthedocs.io/en/latest/Contribute.html#debug-application-problems

Anyway, I am not sure even if there is actually a problem here. Please do more efforts and try to use the application... only then provide feedback there. ty

I still got no answers from these questions I made, so, aside the network problem, we have no way to help you if you don't help us understand your current situation.

The problem with Tor is not a reason enough to say that the application is not working. With your docker ps command is clear that all the services are up and running so you don't have to stop once you get a generic error from the console.

[0ssigeno]

So, as Matteo said, having the cron for Tor not working does not mean the application is not working: the important issue that i saw in your screenshot were the one between the containers, not between a container and the tor url.

Having said that, you can disable the Tor analyzer (django admin -> analyzer configs -> torproject -> disabled -> save) and this will disable the cronjob too.

[ccw2777]

Here are a few screenshots of the errors from the log files you mentioned.