I have a number of services I’d like to host, and an old laptop with some of them set up and working on my network.

But I currently have a Google router, and the Google home app doesn’t seem to let you port forward. The “Port Management” option in Advanced Settings redirects to privacy settings.

There’s one port I forwarded before the app broke a few years ago, but I don’t suppose it’s viable to run multiple services through a single port.

Is there a workaround, or am I stuck until I can get a new router?

  • Bolt@lemmy.worldOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I have the same app version and my account has “Manager” permissions, which seems like it should be enough by the description.

    Are there other types of permission?

    • effingjoe@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Manager is the highest. (I think there are only two tiers anyway.)

      There is something uniquely wrong with your setup; this is not a general google router issue. Which is good news, you don’t need a new router. The next obvious step (for me) would be to wipe the data for the Home app on the phone and re-set it up. If that doesn’t resolve it, you might consider resetting the router itself to factory, though that could be more annoying.

      • Bolt@lemmy.worldOP
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        I’ve tried factory resetting the router, and have reinstalled the app several times. I think I’ve gotten, if not to the source, than further down the chain.

        1. Port Management requires cloud services, which is why it redirects me to the place where I can enable that.
        2. However when I try enabling it, it is “Unable to save settings.”
        3. I tried to “Restart entire network” which revealed that it is “Unable to communicate with your network at this time.”

        And that’s the core thing I don’t know how to get around. The app can’t actually interact with the network. That explains why restarting the network hasn’t fixed it in the past. I don’t understand how it could be an issue only I have though, since it happens regardless of reinstalling the app.