Karatekid

Members
  • Posts

    36
  • Joined

Posts posted by Karatekid

  1. Hi,

     

    I have a AVM GmbH Fritz!Card PCI v2.0 ISDN and I want to passthrough the card to Windows but I got a error.

    I googled this error but don't find a solution. Hopefully you can help me.

     

    "Failed to set up TRIGGER eventfd signaling for interrupt INTX-0: VFIO_DEVICE_SET_IRQS failure: Device or resource busy"

     

    image.thumb.png.86bacdef0a2d72f98e96b5a3bbc7b70f.png

     

     

    I tried different PCIe ACS override settings but no change.

     

    VMS Error attached.

     

     

     

     

    VMS_error.txt

  2. 18 hours ago, Djoss said:

    Since it seems that the header is duplicated, did you try to remove it from the proxy host config? You can also use the browser's developper tools to check which headers are added.

    Found the failure in the nextcloud config.

     

    Thank you very much for your help!!

    Have a happy new year.

  3. 10 hours ago, Djoss said:

    You can check your site with https://securityheaders.com to see if the header is correctly set or not.

     

    Also, if the change under the Advanced tab didn't help, try adding "add_header X-Frame-Options “SAMEORIGIN” always;" instead.

    Funny...

     

    https://securityheaders.com/ says:

     

    X-Frame-Options = SAMEORIGIN (green)

    but

    Warning:

    X-Frame-Options --> There was a duplicate X-Frame-Options header.

     

     

    https://scan.nextcloud.com/ says:

     X-Frame-Options is red

     

    Will the X-Frame-Option not set by the last webservice in the row or how does it work?

    Maybe its a poblem by Nextcloud directly.

  4. 6 hours ago, ElectricBrainUK said:

    Hey Karatekid,

    Sorry it's not working for you. Does the UI work and show and control the dockers as you'd expect? Or does it not work their either? Does it connect to your mqtt broker at all? 

     

    Regarding why I chose the route I did for mqtt was just because I'd only integrated it with Homeassistant for my personal use and I liked posting a single topic per device and several topics for the switches and sensors. That doesn't mean I'm not open to adapting it to suit your needs better. Perhaps we should talk on discord though if there will be a lot of back and forth about that? Your call though 

    Hey,

     

    sorry I also forget that you made awesome work!! I would like to have the ability to do something like it.

     

    The UI just shows some dockers and not all of them.

    MQTT is now working, was because of my network structure.

    I need to made that all containers are able to speak to each other and also to unraid.

     

    I thought on a structure like that, where all points have a single message.

    Json is fine but I think at smarthome systems its better to have single messages for every status. 

    That makes it easy to put it as a new json together for the display.

    I checked my adapters at iobroker and see that for example kodi does put every channel or switch in a single message/object.

     

    servername
        systeminfo
            arrayStatus
            arrayProtection
            ...
        vm
            vm1
                switch_1
                id
                status
                usb
                    name
                    attached
                ...
                
        docker
            container1
                switch_1
                imageUrl
                name
                status
                ...

  5. Not working for all of my docker containers at my side.

     

    Log says:
    There was a problem retrieving a field for a docker image
    Cannot read property 'contents' of undefined

     

    Docker images will be build on my side over docker-compose and not over the app center.

     

    what do you need for analysis?

     

     

    Question by the way.

    Why did you not build a general unraid-mqtt-interface?

    I'm using iobroker and nodered and this has not the format of Home Assistant.

    I must no badly change this to my needs.

    So the idea could be a general unraid-mqtt-interface and adapter for every smarthome-system if needed.

  6. On 12/16/2019 at 1:12 AM, Djoss said:

    I forgot that the X_FRAME_OPTIONS variable if for the web interface if NginxProxyManager itself...

     

    Did you try to add the following under the Advanced tab of your proxy host?

     

    
    add_header X-Frame-Options "SAMEORIGIN";

     

    Nextcloud reported that the X-Frame-Option is not configured as "sameorigin".

    Is there a way to check debug this? Maybe there is a wrong Nextcloud setting.

  7. On 12/13/2019 at 3:24 AM, Djoss said:

    You mean the the HTTP header still has the wrong value?  Did you correctly set the variable ?  It should be X_FRAME_OPTIONS with value sameorigin.

    This is my docker compose file  

     

      nginx-proxy-manager_all:
            container_name: Proxy-Manager-All
            image: jlesage/nginx-proxy-manager
            ports:
                - "8181:8181"
                - "8080:8080"
                - "4443:4443"
            environment:
                - X_FRAME_OPTIONS=sameorigin
                - TZ=Europe/Berlin
                - USER_ID=99
                - GROUP_ID=100
            volumes:
                - /mnt/user/XXX/nginx-proxy-manager:/config
            networks:
                internal:
                    ipv4_address: 172.X.X.7
                br0:
                    ipv4_address: 192.X.X.6
            restart: always

     

  8. Hi everybody,

     

    I just updated to 6.8.0 and have now the problem that docker is really slow and also if i create docker containers with docker-compose it is not working as smooth as before. It takes much more time or is not working at all.

     

    I get following error messages:

     

    ERROR: for Krusader  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=70)

    ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
    If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

     

    there is a endless loop of:

    compose.parallel.feed_queue: Pending: set()

     

    And 

     

    compose.parallel.parallel_execute_iter: Failed: <Container: Krusader (d02733)>
    compose.parallel.feed_queue: Pending: set()

     

     

    Has anybody the same problem and a solution for this problem?

  9. Has someone find a solution for these nextcloud error?

     

    "The "X-Frame-Options" HTTP header is not set to "SAMEORIGIN". This is a potential security or privacy risk, as it is recommended to adjust this setting accordingly."

     

    I found nothing which is working.

     

    I added the env variable but this was not fixing my problem.

     

    Hopefully someone has managed it :)

  10. On 4/13/2019 at 4:22 AM, Djoss said:

    This page is used as the default site, when you try to access something that is not configured.  So you can't use it as a static web page.

    Ahhh :D And currently there is no port for a normal static side

     

    On 4/13/2019 at 4:22 AM, Djoss said:

    Can't you use subdomain instead? It's much easier to setup.

    I only have 10 subdomains :/ this is why i wanted to use subfolders. But I see that this highly complicated.

     

    On 4/13/2019 at 4:22 AM, Djoss said:

    I did a quick test with unRAID, and the problem is that its web interface references ressources by absolute paths... so I think it's not possible to reverse proxy it the way you want.  It may be the same problem for NPM...  You can open your browser's developper tools and see the paths of the ressources it try to access.  You should see that a lot of them are not accessible because they are not under the proxy's subfolder.

    Yes correct you are fully right. For that there are complex rules to forward it which I'm right now not fully understood. But you need to pass every main folder he want to access to the proxy.