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

[Temporary Fix] Cactbot not working? Read here #111

Open
hmm-norah opened this issue Aug 26, 2024 · 1 comment
Open

[Temporary Fix] Cactbot not working? Read here #111

hmm-norah opened this issue Aug 26, 2024 · 1 comment

Comments

@hmm-norah
Copy link

hmm-norah commented Aug 26, 2024

You (person having issues with Cactbot) will want to replace the URLS in Browsingway etc. with ones that don't use the IINACT proxy url.

Raidboss Timeline

http://overlayplugin.github.io/cactbot/ui/raidboss/raidboss.html?alerts=0&timeline=1&OVERLAY_WS=ws://127.0.0.1:10501/ws

Raidboss Alert

http://overlayplugin.github.io/cactbot/ui/raidboss/raidboss.html?alerts=1&timeline=0&OVERLAY_WS=ws://127.0.0.1:10501/ws

Combined Alerts & Timeline

http://overlayplugin.github.io/cactbot/ui/raidboss/raidboss.html?OVERLAY_WS=ws://127.0.0.1:10501/ws

Config Window

http://overlayplugin.github.io/cactbot/ui/config/config.html?OVERLAY_WS=ws://127.0.0.1:10501/ws

Basically, just swap http://proxy.iinact.com/overlay/ with http://overlayplugin.github.io/

You should be able to change any problematic cactbot URL using this as a reference. Discord sucks for trying to use for information, so hopefully this will help, credit to the help-general channel for finding this fix.

@marzent
Copy link
Owner

marzent commented Aug 26, 2024

I have no idea what these spam comments are, but they do not contribute to the solution of the issue here...

@astyrah astyrah mentioned this issue Oct 7, 2024
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
@hmm-norah @marzent and others