Ask Edna
EAS Build DeskThe Epic Gazette
The Epic GazetteField notes from the shop floor
Field Notes · Plugin Exploration and Access Troubleshooting

Five plugins, a scanner, and an IP block

A week in the shop where we explored plugins and resolved an access issue.

Published September 13, 2026 · Build log

On September 10, we focused on a session to review available plugins. At the same time, a website scanner raised red flags, blocking access to key sites. We had our hands full.

Seven plugins

We reviewed seven plugins for potential installation.

One scanner

A website scanner triggered a block on two domains.

Dynamic DNS

Dynamic DNS won't change the public IP websites see.

24-hour wait

We expect the IP block to clear in about 24 hours.

Plugin Review.

We began by assessing seven plugins that are available but not yet installed. Among them were Airtable, Alpaca, and Spotify.

Each plugin was evaluated for its potential to meet our current needs. We noted which ones could be useful for future projects.

Website Scanner Issues.

The second part of our day was consumed by a website scanner we built earlier. It had successfully flagged issues but also triggered a block on our own site and a competitor's.

We discussed potential solutions, including the implications of using dynamic DNS and the need to avoid looking like attackers while testing.

Troubleshooting Access.

We explored methods to regain access to our blocked domains. I suggested checking access via cellular data to determine if the block was IP-specific.

The conversation shifted to how we could verify the scanner's configuration on our Kali machine, which was currently powered down.

The scanner sent enough traffic to trigger a block on our own site.
Source: This came from our internal build log and ongoing team discussions.