Evil portal does not work

[M4R3K]

Hello,

I purchased my Pineapple mark VII and I am really sad because the Evil Portal module does not work. I can start webserver, start evil portal, create new portal without problem. The problem is when activating concrete portal. When I click the activate button on some created portal, nothing happened, so the whole evil portal does not work without activated portal. Does anyone know why is this happening and its solution? Is there some way how do activate concrete portal with ssh if this approach within GUI does not work for me?

Thanks,

MK

[M4R3K]

Evil portal version: 1.1

Firmware version: 1.0.1

Connected to internet: Yes

Log:

2021-01-25 11:52:00,504 - evilportal - DEBUG - Initializing module evilportal. (module.py:24)
2021-01-25 11:52:00,530 - evilportal - INFO - Starting module... (module.py:189)
2021-01-25 11:52:00,537 - evilportal - DEBUG - Binding to socket /tmp/modules/evilportal.sock (module.py:191)
2021-01-25 11:52:00,545 - evilportal - DEBUG - Listening on socket! (module.py:194)
2021-01-25 11:52:00,554 - evilportal - DEBUG - Calling 1 startup handlers. (module.py:196)
2021-01-25 11:52:00,607 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:00,612 - evilportal - DEBUG - Calling handler for action check_dependencies and passing {'module': 'evilportal', 'action': 'check_dependencies'} (module.py:108)
2021-01-25 11:52:01,637 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:01,646 - evilportal - DEBUG - Sending response {"payload": {"installed": true, "installing": false, "job_id": null}} (module.py:83)
2021-01-25 11:52:01,742 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:01,750 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/pineapple/ui/modules/evilportal/assets/permanentclients.txt'} (module.py:108)
2021-01-25 11:52:01,760 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:01,766 - evilportal - DEBUG - Sending response {"payload": "172.16.42.42\n"} (module.py:83)
2021-01-25 11:52:01,847 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:01,874 - evilportal - DEBUG - Calling handler for action status and passing {'module': 'evilportal', 'action': 'status'} (module.py:108)
2021-01-25 11:52:02,469 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:02,479 - evilportal - DEBUG - Sending response {"payload": {"running": false, "webserver": true, "start_on_boot": false}} (module.py:83)
2021-01-25 11:52:02,531 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:02,562 - evilportal - DEBUG - Calling handler for action list_portals and passing {'module': 'evilportal', 'action': 'list_portals'} (module.py:108)
2021-01-25 11:52:02,588 - evilportal - DEBUG - Creating portal folder (module.py:473)
2021-01-25 11:52:02,654 - evilportal - DEBUG - Listing directories (module.py:476)
2021-01-25 11:52:02,688 - evilportal - DEBUG - Building list (module.py:479)
2021-01-25 11:52:02,768 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:02,807 - evilportal - DEBUG - Sending response {"payload": [{"title": "Basicportal", "portal_type": "basic", "size": 4096, "location": "/root/portals/Basicportal", "active": false}, {"title": "Targetedportal", "portal_type": "targeted", "size": 4096, "location": "/root/portals/Targetedportal", "active": false}]} (module.py:83)
2021-01-25 11:52:02,927 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:02,950 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/tmp/EVILPORTAL_CLIENTS.txt'} (module.py:108)
2021-01-25 11:52:02,983 - evilportal - ERROR - Exception occurred while reading file:  (module.py:462)
2021-01-25 11:52:03,031 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:03,055 - evilportal - DEBUG - Sending response {"error": ""} (module.py:83)
2021-01-25 11:52:19,448 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 11:52:19,478 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'Basicportal'} (module.py:108)
2021-01-25 11:52:19,563 - evilportal - ERROR - NO EP FILE FOUND: /www/google-login.ep (module.py:53)
2021-01-25 11:52:19,622 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 11:52:19,663 - evilportal - DEBUG - Sending response {"error": "Error activating portal."} 

[chrizree]

Have you used some already existing portal as a "template" when creating your own portal? It seems to load Basicportal and Targetedportal, but at the same time it throws an error not finding a file that is a part of the Google capture portal

[M4R3K]

Yes, using SSH I tried to copy portals from https://github.com/kbeflo/evilportals ... it did not work, so I removed them, reinstall Evil portal Module, even tried to reinstall firmware. Still does not work.

[chrizree]

ok, strange... are you using/testing the "pre-built" portals at all or just your own ones?

[Foxtrot]

As the log you pasted mentions, it cannot find the .ep file for the portal. Make sure it exists at the right path.

[M4R3K]

Just these ones from this github page.

[M4R3K]

@Foxtrot I tried to copy portals from github page above via ssh. It did not work. So I delete them, uninstall Evil Portal, Reinstall firmware and it still not work. How can I make sure that .ep file exits in path for the right evil portal? I removed the portal with google-login. Is it in some configuration file?

[chrizree]

I just upgraded my Mk7 to the freshly released 1.0.2 stable firmware and then I did everything from scratch regarding Evil Portal and it works without any problem, how do you "install" your portals from GitHub?

[M4R3K]

@chrizree By this tutorial: 

 

 

 

[chrizree]

OK, it should work, the ep files should be in the folder for the respective capture portal under /root/portals (i.e. /root/portals/(whatever-name-for-the-portal) )

This is how I do it (using ssh on the pineapple):

opkg update
opkg install unzip
cd /root/portals
wget https://github.com/kbeflo/evilportals/archive/master.zip -O master.zip
unzip master.zip
mv /root/portals/evilportals-master/portals/* /root/portals/.
rm -r /root/portals/evilportals-master
rm master.zip

 

[M4R3K]

I tried exactly the same, and nothing changed and get this result in log:

2021-01-25 23:06:55,848 - evilportal - DEBUG - Initializing module evilportal. (module.py:24)
2021-01-25 23:06:55,875 - evilportal - INFO - Starting module... (module.py:189)
2021-01-25 23:06:55,882 - evilportal - DEBUG - Binding to socket /tmp/modules/evilportal.sock (module.py:191)
2021-01-25 23:06:55,887 - evilportal - DEBUG - Listening on socket! (module.py:194)
2021-01-25 23:06:55,900 - evilportal - DEBUG - Calling 1 startup handlers. (module.py:196)
2021-01-25 23:06:55,968 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:06:55,978 - evilportal - DEBUG - Calling handler for action check_dependencies and passing {'module': 'evilportal', 'action': 'check_dependencies'} (module.py:108)
2021-01-25 23:06:57,090 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:06:57,097 - evilportal - DEBUG - Sending response {"payload": {"installed": true, "installing": false, "job_id": null}} (module.py:83)
2021-01-25 23:06:57,168 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:06:57,175 - evilportal - DEBUG - Calling handler for action list_portals and passing {'module': 'evilportal', 'action': 'list_portals'} (module.py:108)
2021-01-25 23:06:57,182 - evilportal - DEBUG - Creating portal folder (module.py:473)
2021-01-25 23:06:57,200 - evilportal - DEBUG - Listing directories (module.py:476)
2021-01-25 23:06:57,220 - evilportal - DEBUG - Building list (module.py:479)
2021-01-25 23:06:57,263 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:06:57,269 - evilportal - DEBUG - Sending response {"payload": [{"title": "google-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/google-login", "active": false}, {"title":>2021-01-25 23:06:57,383 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:06:57,407 - evilportal - DEBUG - Calling handler for action status and passing {'module': 'evilportal', 'action': 'status'} (module.py:108)
2021-01-25 23:06:58,015 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:06:58,022 - evilportal - DEBUG - Sending response {"payload": {"running": false, "webserver": true, "start_on_boot": false}} (module.py:83)
2021-01-25 23:06:58,079 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:06:58,119 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/tmp/EVILPORTAL_CLIENTS.txt'} (module.py:108)
2021-01-25 23:06:58,128 - evilportal - ERROR - Exception occurred while reading file:  (module.py:462)
2021-01-25 23:06:58,168 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:06:58,194 - evilportal - DEBUG - Sending response {"error": ""} (module.py:83)
2021-01-25 23:06:58,483 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:06:58,530 - evilportal - DEBUG - Calling handler for action load_file and passing {'module': 'evilportal', 'action': 'load_file', 'path': '/pineapple/ui/modules/evilportal/assets/permanentclients.>2021-01-25 23:06:58,569 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:06:58,606 - evilportal - DEBUG - Sending response {"payload": "172.16.42.42\n"} (module.py:83)
2021-01-25 23:07:02,263 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:07:02,285 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'google-login'} (module.py:108)
2021-01-25 23:07:02,324 - evilportal - ERROR - NO EP FILE FOUND: /www/google-login.ep (module.py:53)
2021-01-25 23:07:02,355 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:07:02,366 - evilportal - DEBUG - Sending response {"error": "Error activating portal."} (module.py:83)
2021-01-25 23:07:09,836 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:07:09,868 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'cliqq-payload'} (module.py:108)
2021-01-25 23:07:09,891 - evilportal - ERROR - NO EP FILE FOUND: /www/google-login.ep (module.py:53)
2021-01-25 23:07:09,897 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:07:09,955 - evilportal - DEBUG - Sending response {"error": "Error activating portal."} (module.py:83)
2021-01-25 23:07:13,224 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:07:13,245 - evilportal - DEBUG - Calling handler for action toggle_portal and passing {'module': 'evilportal', 'action': 'toggle_portal', 'portal': 'cliqq-payload'} (module.py:108)
2021-01-25 23:07:13,311 - evilportal - ERROR - NO EP FILE FOUND: /www/google-login.ep (module.py:53)
2021-01-25 23:07:13,345 - evilportal - DEBUG - Accepting on module socket (module.py:79)
2021-01-25 23:07:13,372 - evilportal - DEBUG - Sending response {"error": "Error activating portal."} (module.py:83)
2021-01-25 23:07:15,101 - evilportal - DEBUG - Processing request. (module.py:211)
2021-01-25 23:07:15,134 - evilportal - DEBUG - Calling handler for action toggle_webserver and passing {'module': 'evilportal', 'action': 'toggle_webserver'} (module.py:108)

[chrizree]

It for sure looks different than my log, see how it cuts when reading the portals...

2021-01-25 23:06:57,269 - evilportal - DEBUG - Sending response {"payload": [{"title": "google-login", "portal_type": "basic", "size": 4096, "location": "/root/portals/google-login", "active": false}, {"title":>2021-01-25 23:06:57,383 - evilportal - DEBUG - Processing request. (module.py:211)

just when it's about to list the next portal (Facebook in my log) it throws a Processing request message, not sure if it has any relevance, but it looks odd

[chrizree]

If you install tree on the Pineapple and position yourself in /root/portals and run the tree command, what does the output look like?

[chrizree]

Another thing that came to mind... in what way do you power your Pineapple? What's your power source? At least 2A? It shouldn't be a reason in this case since the errors are pretty consistent but it's always good to be sure that enough power is supplied to the Pineapple.

[M4R3K]

SOLVED

Found the solution. Before I first time copied portals via ssh, I renamed the folders with en profix (google-login -> en-google-login). Then in /www folder remained symlinks to non-existing folder. Solution is to update these symlinks and restart pineapple.

[Traxxas]

I got the same error M4R3K, i delete the EP file who cause the problem, but for me i still having the same issue i have a mark 7 and il try to reinstall the firmware, reinstall dependencys and evil portal again and nothing, somebody can help me pls?

[Mental]

On 2/15/2021 at 2:42 AM, Traxxas said:

I got the same error M4R3K, i delete the EP file who cause the problem, but for me i still having the same issue i have a mark 7 and il try to reinstall the firmware, reinstall dependencys and evil portal again and nothing, somebody can help me pls?

Yeah same here, defo would love to find a fix to it!

[Watt22]

Hey guys,

my name is Simon and it seems that I'm dealing with the same issue. I've have manually uploaded a portal (evil portal) via Filezilla und renamed it afterwards. Therefore I must say, that I am completely new into Pineapple and Linux which is why I used FTP transfer instead of SCP. However, now I am not able to activate any portal anymore as it says it "is unable" to.

What did I do so far?

I've renamed the folder back to the origin name but that didn't solve the issue. After that I've simply copied the command which can be seen in @M4R3Ks screenshot and the result is as follows:

Can anybody help me fixing this?

Thank you guys in advance!

[Watt22]

7 hours ago, Watt22 said:

Hey guys,

my name is Simon and it seems that I'm dealing with the same issue. I've have manually uploaded a portal (evil portal) via Filezilla und renamed it afterwards. Therefore I must say, that I am completely new into Pineapple and Linux which is why I used FTP transfer instead of SCP. However, now I am not able to activate any portal anymore as it says it "is unable" to.

What did I do so far?

I've renamed the folder back to the origin name but that didn't solve the issue. After that I've simply copied the command which can be seen in @M4R3Ks screenshot and the result is as follows:

Can anybody help me fixing this?

Thank you guys in advance!

sry, the image doesn't work anymore. Here it is again:

[chrizree]

Just try something that is known to work first, like kleo's portals. You can use my script on my GitHub repo and run it directly from the Mk7 so that you don't need to involve any intermediate copying. Also, the files are placed in the intended location with the correct names and structure.

https://github.com/chrizree/PineappleEPfix/blob/main/just_add_the_portals.sh

[Watt22]

Thank you @chrizree! Unfortunately it still won't start any portal. Do you guys think a reset to factory settings will work for me? Or will the corrupt symlinks remain?

[chrizree]

This shouldn't be a problem at all. I set up/install the Evil Portal module (with portals) pretty often since I reset my Mk7 several times for different reasons and it never fails. If you have messed around with the file system, I would probably do a firmware recovery and start over fresh if it was me. If doing so, remember to copy/backup anything that you want to save from the Mk7. Also make sure to be on the latest firmware.

[Watt22]

Yessss, that worked... Everything works great again! Thank you!

[Joe Smith]

So, it works great on first install of latest firmware. But if I install a portal from Kleo, then it breaks and the only fix is to flash. Period. End. Of. Story. Even if I delete the portals, uninstall the module and reboot then reinstall the module and add a new portal from the button:  NOGO! Flash, reinstall the module, new portal from the New Portal button: GO! Install a portal from any source other than the New Portal button: NO EFFING GO!

This is consistent. 100% of the time. Firmware  is 2.1.3

But hey, this is the kind of instability and bugginess I've just learned to deal with since I bought this thing version 1.0.