Just checked and the deletion case was ok but not rename. https://github.com/bsdperimeter/pfsense/commit/bb83746870f64525e477e1ddd14adc56b894b758 Easy fix. Would also fix itself on reboot when the users are cleaned up and resynced. For a quicker fix that doesn't require editing and files, go to Diagnostics > Command and run this in the PHP exec box: require_once("auth.inc"); local_sync_accounts();

@pffan: Gah! What we have here is an instance of browsers behaving badly.  I didn't realize what the problems was at the start because both IE and Firefox demonstrated the same behavior.  Once I tried Chrome however, everything worked as expected.  I think that because I had previously connected to the webGUI on http port 80 with both my browsers before, it kept pulling the cached page on my subsequent attempts and this is what was causing the redirect to https custom port.  Once I cleared the history and cache, everything is working as expected. Hopefully someone else can benefit from this information. I did, I run into same problem, thanks.

@phil.davis: I am using Firefox11 on Windows7. It works fine for me uploading to a nanobsd system, on 2.0.1 and 2.1. After browsing to the file then pressing upload the top of the display says: Uploaded file to /tmp/filename and executing "ls -l /tmp/filename" lists the file as expected. So there must be something else special about your environment. I'm seeing some problems for sure, I guess that Squid f*cked more stuff up somehow perhaps then.. This was a freshly installed box though, actually only the various Squid packages have been added and messed with. I guess I'll do a reinstall soon if things don't start to work as expected.

Registered as Bug #2326.

@martinjsaunders: When I reload the config the group seems to correctly reflect the new privaleges above, missing the Bridge pages (plus a few others I removed), but the pages are still accessable and I can still Bridge interfaces. Have I done something silly? Thanks very much in advance! M. To answer my own question, if I add a new users in the group Admins it inherits the correct permissions. This is fine but I'd rather disable admin for Bridging as well, is the admin user inheriting it's permissions from somwhere else as well?

Historically, "Load Balancing" has applied to both incoming and outgoing. It's only in 2.x that we've split the outbound LB actions into a separate place (Gateway Groups). Sticky applies to both.

You mean use pfsense as a web server? If so, there is a package for it. if you want to do it by Hand, change webgui port, create/copy lighthttp config and start it as a second web server.

Thanks. I'll take the risk, as the web interface is only accessible on a private LAN and through VPN.

….whoops - 3000 is nTOP

Hi ! First things first. Check out this page: http://www.pfsense.org/ This somewhat implies that "2.0-Rc3" is abandoned. So: upgrade  ;)

That's a fairly old version of the code, but yeah that's the part. It actually works fine on Android which is odd because Android's browser and the iOS browser are both webkit. Though the theme may work, the other theme does tend to handle better on small screen devices anyhow, it's really easy to miss the menus when they drop-down.

@cmb: That has no relation to #637 but may be a separate issue, open a new ticket in redmine if you can reliably replicate that. done, Sir! :D -> http://redmine.pfsense.org/issues/2253

Hi, I think that I'm near solution for my problem. As I mentioned I'm using Option Icon 225 3G modem and that is the problem. This modem need its own driver not the one compiled in pfsense (u3g). I compile correct driver (uhso) on freebsd 8.1 to get uhso.ko file, I put that file in boot/kernel and in kernel.conf I added the line uhso_load="YES". When I attach my usb card it try to use uhso driver but it get detached immediately and than reattached and load u3g driver. Can I, somehow, disable u3g driver? This is driver compiled with kernel. Thanks, Nikola

Ok, found the problem. Firefox was defaulting to http.  added https://externalwaipip:8443 and it works! Didnt need the NAT rule in the end.

Really was scratching my head on this one not to worry I was just trying out HTTPS trying to get my router a little more secure so to speak. I accidentally yea locked myself out as I said, but couldn't work out why I couldnt get in when I'd reset for some strange reason it had made 2 rules of the same exact settings for HTTP, hmm weird but oh well I will leave it be for now and when I get back home will work out why. There is an option when I do a setting in the SSH login (remotely in my case) to reset back to HTTP and reset the password but I can't remember actually thinking back to which one includes the HTTP reset, but it did work and thank you again I mean I just deleted the first rule I had of HTTP and it let me back in weird though oh well least it's working now. Thank you ever so much for your help, Jeremy.

Thank you I didn't look deep enough on the firewall rule set. Coming from another FW I didn't have to set any rules to pass traffic.

I do remeber reading something to that effect.Sorry for placing a question already covered. Thank You for your time:)