Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    nginx Errors in 23.01 from iPad Air?

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 243 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sammiorelli
      last edited by

      I have had a ton of instability since upgrading from 22.05 to 23.01 particularly around unbound. Those seemed to be fixed by turning off some VPN services I was not using and installing System Patches.

      But I'm still getting a ton of the following errors and I can't really figure it out. Any ideas? The client mentioned is an iPad Air.

      May 13 16:07:24 nginx 2023/05/13 16:07:24 [error] 45478#100096: *1 open() "/usr/local/www/simpleM2M/clientRequestEnhancedXmlAd" failed (2: No such file or directory), client: 192.168.1.206, server: , request: "POST /simpleM2M/clientRequestEnhancedXmlAd?userid=ff6d1c5d-d541-40dc-9ccd-c06110f20a75&protocols=2%2C5&low_power_mode=0&tod=-240&crn=iPad&mcc=310&f=372&btry_l=6&appv=1.14.4&pxratio=2&h=1180&bid=com.peoplefun.blockscapes&dml=iPad13%2C1&skadnetwork_version=3.0&mute_video=true&spotid=203120&appb=1878&med=MAX_11.4.1&sdur=665&mnc=300&dark_mode=0&api=5%2C7&dsk_t=244124&us_privacy=1---&o=p&lng=en&osv=16.3.1&secure=0&idfv=BB42B325-8A64-4A22-872D-87EF671BE5C1&frmn=unity3d&ciso=us&nt=wifi&app_trk=2&os=iOS&dsk_a=157796&t=1684008444027&v=2.2.0-iOS-8.1.3&w=820&in_lng=en-US&headset=0&fromSDK=true&mimes=video%2Fmp4%2Cvideo%2Fm4v%2Cvideo%2Fquicktime%2Cvideo%2F3gp2%2Cvideo%2F3gpp2%2Cvideo%2F3gp4%2Cvideo%2F3gpp4&btry_c=0&dnt=true HTTP/2.0", host: "wv.inner-active.mobi"

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        It's trying to open pages that don't exist in pfSense. It probably was previosuly connected to something at the pfSense IP and hasn't updated yet.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.