Comment 18 for bug 1664248

I am getting a 404 now. I can take another screenshot if you want. That screenshot was not completely applicable to this specific issue, I found that I concurrently had another issue when I was trying to report it. I was getting a 403 from the maas server since for some reason it did not add my subnet to the internal proxy. I need to figure out why maas is not setting the values for that subnet like it should. I would also like the ability to manually specify values for that config. It is helpful to set a proxy peer and have a no proxy settings. Currently I am just stomping over the file with chef and not letting maas update it, and could just set up another server. But while that works it is not the best of solutions.