Evil Portal / Captive Portal: Error activating portal

[unamed]

Hi everyone!

I'm doing some stuff with captive portal. Everything went well until I wanted to make my own.

I was successfully upload evil portals from https://github.com/kleo/evilportals but when I upload my own, I've got 

Error activating portal

 

• Evil Portal Version: 1.4
• Pineapple version: 1.1.1
• Are you connected to the internet?: Yes
• The output of the module log file located at: /tmp/modules/evilportal.log on your pineapple.:

  • 2022-02-15 14:18:50,180 - evilportal - ERROR - NO EP FILE FOUND: /www/<name_of_my_module>.ep (module.py:53)

    2022-02-15 14:18:50,212 - evilportal - DEBUG - Accepting on module socket (module.py:85)

    2022-02-15 14:18:50,244 - evilportal - DEBUG - Sending response {"error": "Error activating portal."} (module.py:89)

I've removed all Captive Portals and installed them again but error still occurs. 

How to get rid of this error and make CP work again?

 

PS:

Sometimes, when accessing Evil Portal module I receiving:

unix /tmp/modules/evil portal.sock: connect: resource temporarily unavailable

 

[dark_pyrro]

Is there any ep file in /www ?

[unamed]

Jest there is:

• MyPortal.php
• <name_of_my_module>.ep
• helper.php
• README.md
• assets
• index.php

[unamed]

I've removed that .ep file from /www folder. 

Once I clicked on any other Captive Portal I've received

Handler raised exception: [Errno 17] File exists: '/root/portals/cliqq-payload/README.md' -> '/www/README.md'

 

[unamed]

My solution:

1. go to Settings
2. Scroll down to Software Update
3. Click on Check For Updates button
4. If there are no updates click this button again
5. message will change on CTA to Reinstall Current Firmware

No effort, no wires, no errors... WHY this is not mentioned anywhere?

Anyways... it's a really good TIP and helpful feature.

After that I created my test Captive Portal which I could Preview

[Layer4Redna]

This solution has worked for me. After running some obscure portals found on GitHub, I began receiving the error "Error activating portal" when attempting to activate any previously working portals.

1. Access /www
   1. Remove all contents excluding the captiveportal directory or its contents.
2. Access /root/portals.
   1. Remove all existing portals you may have added.
3. Prepare to transfer original portal files from your host to the Pineapple.
   1. In each portal directory, for example facebook-login, remove the enable and disable files.
   2. Re-transfer each of the evil portal directories to the /root/portals path.
4. Access Pineapple Evil Portal module and attempt to activate.

TLDR: On the pineapple, remove everything from the www folder but the captiveportal folder. Then delete all files in the /root/portals. In your Kleo EvilPortal repo clone, delete the enable/disable files from each of the portal folders and re-add them to the /root/portals path.

Hope this helps, it has worked for me each time I have tried using a non-working evil portal.

Notes: Portals I tested and found not working. These resulted in errors when activating other portals.

1. JonnyBanana/Netflix_EVIL_PORTAL
2. gscamelo/evilportals Microsoft SSO Evil Portal
3. LuemmelSec/evilportals ADFS Evil Portal

[Wind010]

I was able to resolve this by deleting all the .enable and .disable files from /root/portals using the following since the -delete flag isn't supported with find in this bash.
 

rm $(find -type f -name '.enable')

rm $(find -type f -name '.disable')

 

[Wind010]

3 minutes ago, Wind010 said:

I was able to resolve this by deleting all the .enable and .disable files from /root/portals using the following since the -delete flag isn't supported with find in this bash.
 

rm $(find -type f -name '.enable')

rm $(find -type f -name '.disable')

 

Correction from the portals directory:
 

rm $(find . -type f -name '.enable')

rm $(find . -type f -name '.disable')

 

[Wind010]

Also cleared out the /www directory:

rm -r /www/*

 

[focus666]

On 1/1/2023 at 1:33 PM, Wind010 said:

Correction from the portals directory:
 

rm $(find . -type f -name '.enable')

rm $(find . -type f -name '.disable')

 

You're way was the way