HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Wireless
- >
- Comware Wireless / Unified Series
- >
- Airconnect giving 502 Bad Gateway messages
Comware Wireless / Unified Series
1836534
Members
4304
Online
110102
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2009 11:58 AM
03-25-2009 11:58 AM
Airconnect giving 502 Bad Gateway messages
Ok we received two units a week ago. They came with 1.4.x firmware, first thing I did was upgrade to latest 1.6.1 firmware, and everything for several days seemed excellent. Then Tuesday morning people said they could not get IP's from the wireless (we disabled the AP dhcp and used in house dhcp server)dhcp works just fine for all hard wired devices.
I then attempted to login to either unit to see what was up and all I got when I attempted to connect to either one was:
502 Bad Gateway
The CGI was not CGI/1.1 compliant.
Now I've gotten this while attempting to hit the unit via ip and by the DNS name we defined for it (and yes there is a reverse dns pointer matchign the name). In the end the stupid solution was to power cycle them and suddenly they worked again.
Now what worries me a hour ago I wanted to check how the spread of machines was working and if I attempt to hit one of the units by it's IP again I'm getting the same error, but by DNS name it's still working. Nobody has complained about any other issues, but.....
So what does that error mean? how do I fix it without power cycling the unit? We purchased these because the previous units from d-link that we had would freak out about once every 4 days when there was a sudden high amount of usage being pushed through them (as in several users pushing multi gig files at the same time), then the radio portion would suddenly just stop working, you could see it via the wifi light that it just shut down.
I can't be sitting here with yet another solution that needs to be power cycled every few days to keep people happy. We are a office of 18 people with 13 wireless devices and two units, one covering one floor and the other for the second floor (we have tried 1 unit and it does not work in the far reaches of the other floors corners with just one).
Also is there a way to get the admin password to stay valid for a connection for a slightly longer timeframe. It seems to be timing out way to quick when I sit and attempt to monitor connections in the morning with people coming in.
I then attempted to login to either unit to see what was up and all I got when I attempted to connect to either one was:
502 Bad Gateway
The CGI was not CGI/1.1 compliant.
Now I've gotten this while attempting to hit the unit via ip and by the DNS name we defined for it (and yes there is a reverse dns pointer matchign the name). In the end the stupid solution was to power cycle them and suddenly they worked again.
Now what worries me a hour ago I wanted to check how the spread of machines was working and if I attempt to hit one of the units by it's IP again I'm getting the same error, but by DNS name it's still working. Nobody has complained about any other issues, but.....
So what does that error mean? how do I fix it without power cycling the unit? We purchased these because the previous units from d-link that we had would freak out about once every 4 days when there was a sudden high amount of usage being pushed through them (as in several users pushing multi gig files at the same time), then the radio portion would suddenly just stop working, you could see it via the wifi light that it just shut down.
I can't be sitting here with yet another solution that needs to be power cycled every few days to keep people happy. We are a office of 18 people with 13 wireless devices and two units, one covering one floor and the other for the second floor (we have tried 1 unit and it does not work in the far reaches of the other floors corners with just one).
Also is there a way to get the admin password to stay valid for a connection for a slightly longer timeframe. It seems to be timing out way to quick when I sit and attempt to monitor connections in the morning with people coming in.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2009 02:00 PM
04-13-2009 02:00 PM
Re: Airconnect giving 502 Bad Gateway messages
Having exactly same issue. Did you ever get this sorted out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2009 02:11 PM
04-13-2009 02:11 PM
Re: Airconnect giving 502 Bad Gateway messages
You should open a case with 3Com support, they will help you troubleshoot your issue.
POM
POM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2009 03:42 PM
09-18-2009 03:42 PM
Re: Airconnect giving 502 Bad Gateway messages
Hello,
Did you ever get anywhere with this? I have the exact same problem... and it happened with the 1.4.x firmware as well - i was hoping 1.6.1 would fix it...
Did you ever get anywhere with this? I have the exact same problem... and it happened with the 1.4.x firmware as well - i was hoping 1.6.1 would fix it...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP