| Summary: | Blank proxy pac after restore on clean 164 install | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Paul Walker <pa_walker> |
| Component: | --- | Assignee: | Peter Müller <peter.mueller> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | Minor Usability | ||
| Priority: | - Unknown - | CC: | adolf.belka, michael.tremer |
| Version: | 2 | Keywords: | 5MinuteJob |
| Hardware: | all | Flags: | adolf.belka:
needinfo+
|
| OS: | All | ||
|
Description
Paul Walker
2022-03-22 10:18:53 UTC
@Peter: Could you please add this file to the backup system? Just performed upgrade to release 165, and the file was blanked again. Save and restart in the proxy config page recreated it. (In reply to Paul Walker from comment #3) > Just performed upgrade to release 165, and the file was blanked again. Save > and restart in the proxy config page recreated it. It was blank *after* you installed the update? That is another problem then. (In reply to Michael Tremer from comment #4) > (In reply to Paul Walker from comment #3) > > Just performed upgrade to release 165, and the file was blanked again. Save > > and restart in the proxy config page recreated it. > > It was blank *after* you installed the update? That is another problem then. Yes, performed update, rebooted, couldn't connect to web interface until I disabled proxy in my browser. Had to save and restart the proxy service to recreate the file so that my PC would pick up the proxy settings. Thank you for confirming. The file should not be overwritten in an update, because it is on the exclude list. @Peter: Could you check why this is going wrong? Apologies for my belated response. Hm, proxy.pac has been in the exclude file for all the 16x Core Updates: oldcore/160/exclude:srv/web/ipfire/html/proxy.pac oldcore/161/exclude:srv/web/ipfire/html/proxy.pac oldcore/162/exclude:srv/web/ipfire/html/proxy.pac oldcore/163/exclude:srv/web/ipfire/html/proxy.pac oldcore/164/exclude:srv/web/ipfire/html/proxy.pac oldcore/165/exclude:srv/web/ipfire/html/proxy.pac oldcore/167/exclude:srv/web/ipfire/html/proxy.pac oldcore/168/exclude:srv/web/ipfire/html/proxy.pac oldcore/169/exclude:srv/web/ipfire/html/proxy.pac It is, however, in the Squid rootfile, but that should not matter if it is in the exclude file. Or am I getting that wrong? Is this issue still valid with Core Updates 175 to 181? I have been using proxy.pac and wpad.dat via DNS and HTTP distribution on my laptop since around CU175 and I have not had any problem where after upgrade and reboot the proxy was not working on the browser. wpad.dat is a symlink to proxy.pac so a blank version would be expected to give a problem irrespective of which file is being looked for. For my desktop I am using the http://[IPFireIP]:81/wpad.dat link from my Web Proxy WUI page in my Firefox Browser, earlier than CU175 and again without any problems during upgrades. On your Web Proxy WUI page is the link shown as http://[IPFireIP]:81/wpad.dat or http://[IPFireIP]:81/proxy.pac If you are still seeing the problem with recent CU's maybe worth trying with the wpad.dat link rather than proxy.pac, although I believe both are the same file. There has been no response to the request for further info for 7 weeks. This bug is therefore being closed. If it is still valid then it can be reopened together with supporting information from the current release. |