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

not working anymore since MM v2.20.0 Upgrade #34

Open
editwentyone opened this issue Jul 11, 2022 · 11 comments
Open

not working anymore since MM v2.20.0 Upgrade #34

editwentyone opened this issue Jul 11, 2022 · 11 comments

Comments

@editwentyone
Copy link

hi,

I love your plugin but its not doing anything since I updated magic mirror to v2.20.0

any idea how to debug that and to fix? :(

would love to see it running again

@JWilson5607
Copy link

I just attempted to install it on mine - I am running the latest as well. What error are you getting? I am getting a refused to connect error, but am able to navigate directly to my page on the computer MM is running on.

image

@JWilson5607
Copy link

JWilson5607 commented Jul 27, 2022

I checked my developer settings and it is the following error: Refused to display 'http://10.0.4.11:3001/' in a frame because it set 'X-Frame-Options' to 'sameorigin'. - I wonder if yours is the same issue or not. I am not sure how to get around this just yet.

Fixed by allowing sameorigin for the docker container i was attempting to connect to

@editwentyone
Copy link
Author

what did you do exactly? maybe I have the same problem, had to disable the plugin for now

@editwentyone
Copy link
Author

@JWilson5607 could you guide what you did?

@johnwilson5607
Copy link

@JWilson5607 could you guide what you did?

Apologies @editwentyone life got busy. I will take a look at is this evening when I get back home and post what I did to fix it. I believe, since I am using unraid as my docker host, that I just added another variable to the container in the menu, but what exactly it was I do not recall.

@JWilson5607
Copy link

@editwentyone louislam/uptime-kuma#1146

See here. I have spun up a docker-compose version as I am wanting uptime kuma over to my pi and not my Unraid box. I am really green with docker and am trying to figure out how to add UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN=1 to the docker-compose.yml file. So far no luck

@JWilson5607
Copy link

JWilson5607 commented Aug 14, 2022

Correction - I had to completely restart the browser to show it after updating the docker-compose.yml file with this:

version: '3.3'

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma-data:/app/data
    ports:
      - 3001:3001  # <Host Port>:<Container Port>
    restart: always
    environment:
      - UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN=1

@editwentyone
Copy link
Author

thanks I will try to figure it out

@AgP42
Copy link
Owner

AgP42 commented Aug 20, 2022

Hello guys,

sorry for not being very active recently and sorry to see that this module is not working anymore.

If you find the modification to apply, please send me a pull request and I will merge it.

Thanks for your collaboration ;-)
AgP

@Dresch360
Copy link

Any updates on this? I've tried all of the methods above and none work.

@CommanderStorm
Copy link

@JWilson5607 Have you tried setting said variable to true?
See our docs on iframes: https://github.com/louislam/uptime-kuma/wiki/Status-Page#custom-subdirectory--custom-html-on-status-pages

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

6 participants