Skip to content
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

Problem with database #18

Closed
haziqahbalqis opened this issue Jan 24, 2019 · 3 comments
Closed

Problem with database #18

haziqahbalqis opened this issue Jan 24, 2019 · 3 comments

Comments

@haziqahbalqis
Copy link

Can anyone know how to fix my problem? I have already get to connect with honeypot.py but when I link with telnet 127.0.0.1 2223 the backend.py cannot read the data.

Thank you

backend py result
honeypot py result
telnet 127 0 0 1 2223

@f1r3walled
Copy link

Hello,
Unhappy, I had no success while troubleshooting the project, like the last time. I tried a lot of possibilities and changes in the configuration files and packages installation, but none worked for me.
The behavior is ever the same, it means, no data is recorded on the database and not even shown on the frontend.
I tried the manual installation and also the procedure through vagrant, but the behavior is the same for both situations.
My error message is referred to the following link "http://sqlalche.me/e/e3q8", but it is not telling enough to finish the troubleshooting.
Anyway, I imagine that this project has ended, because there is no updated since more than one year ago.
I'll fork it to work in an improved version.
If your project or curiosity is related to honeypot, I recommend you MHN (https://github.com/threatstream/mhn), which is a great project and largely supported by the community.

Cheers!

@haziqahbalqis
Copy link
Author

Thank you sir for try to solve my problem but can I ask something? there are possible or not if we save the data at backend record to txt file and display the data in independent webpage?

@Phype
Copy link
Owner

Phype commented Mar 5, 2019

As already mentioned somewhere else, i could not reproduce these errors. However i chnaged basically the whole project in the last commit (actually, the these changes were made during half of a year), so maybe they just went away?

@Phype Phype closed this as completed Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants